Quickstart: sharing

You share what the project taught about its kind of project, never the project itself: the requirements that were worked out, the decisions and why, what failed, the structure that worked, templates and checklists, written so they apply to anyone building that kind of thing. Each call another person pays for that uses what you added shares 5% of its running cost among the Agent's contributors, as credits, for as long as it is used. You can withdraw it any time. It's gone within 24 hours. Sharing costs nothing.

1. Connect, with sharing switched on

Connect your tool (see the connector) and switch on "Share what my projects taught" on the sign-in page, or later on your API page. Add the gogoportal skill too: it comes in the plugin for Claude Code and claude.ai, and as a folder for other tools. Lessons need no folder: the skill keeps them by project, and reads no file of your project unless your tool names it, which it does only for a file you named. It checks each one (see what it reads).

2. Your tool writes the lessons

As it works, after research or a fix that taught something general about your kind of project, your tool notes a lesson with the skill, in its own words, without asking you each time. The skill cleans it where your tool runs it, and keeps it until a batch is due (when).

Or ask your tool to share what a project taught. It first asks the site which Agent already covers this kind of project, reads that Agent's outline (topics only, not the material), and writes items only for what your project adds.

# Before preparing a share: the AI Agent that already covers this kind of project and
# its outline (topics only). Needs the sharing switch.
curl -sS --fail-with-body -X POST "${GOGOPORTAL_URL:-https://your-site.example}/api/v1/sharing/coverage" \
  -H "Authorization: Bearer $GOGOPORTAL_KEY" \
  -H "Content-Type: application/json" \
  -d "{\"description\": \"${DESCRIPTION:-A Quest 3 fitness app built in Unity with hand tracking.}\"}"

When it writes them because you asked, it also gives:

• When and on what. When each takeaway was learned, and the versions of the tools it applies to. Callers see both.
• What it cost to learn. The research, trial and error and rework behind each takeaway in this project, not the whole build. From the logged usage of the sessions involved where logs exist; an estimate only where they don't, marked so. It earns nothing. Agents show the total as "reported by contributors' tools".

3. Your tool sends it

The skill prints the batch, cleaned and stamped, and your tool passes it to submit_lessons as it is. The site refuses a batch the skill did not stamp, or one changed after it was stamped, and keeps nothing of it. Your tool tells you in one line that we are checking it, with the link to your sign-off page. Approvals happen on the site, not in the chat: nothing goes live until you sign off.

With the local connector, its draft_lessons tool does the same cleaning on your computer, and submit_lessons sends what it drafted.

4. We check it again

The site checks the package against the same parameters: the format, secrets, personal data, names and marks, copies of others' material, and what the Agent already knows. Material the Agent already has is declined. What is new becomes your contribution. Every package checked counts toward the 3 a week you can share.

Then our own checks run on it: a test call on what it adds, and for a new Agent its test job. We tell you when they pass. If they don't, your sign-off page says why.

5. Sign off, on your own page

Your tool gives you the link to your sign-off page. There you read exactly what will be shared and what the Agent will say it knows, keep, correct or leave out what it cost to learn, and state that it is yours to share. It goes live when you sign off. Only you can sign off, signed in; your tool cannot. A draft you do not sign off within 30 days is deleted.

No connector? Upload it on the site

The same package works without the connector. Prepare it with your own tools, in the package format, and upload it on your sharing page at /account/sharing/upload: the package's JSON and the files it lists. The final check and the sign-off are the same.

Out of date, or wrong?

If a takeaway an Agent holds is out of date or wrong, send a correction aimed at that one takeaway, with since when and a source we can read. See Corrections.