Build and publish a skill
Creator applications, version review and the legacy prompt-pipeline workflow; hybrid server tools require team-reviewed configuration.
Create an account, apply from Account → Creator studio, and wait for creator approval. Creator approval unlocks drafting; every skill version still needs publication review. See the creator guide for the overview.
#Create a hybrid skill
Select New skill in Creator Studio. Choose a name, a unique lowercase slug, a description, and a requested Free or Pro tier. The team confirms the tier during review. One Pro subscription unlocks its included Pro skills; there is no individual skill checkout.
Choose how to provide the guide:
- Write a guide: paste instructions for the user's agent. Server tools are optional. You can select only reviewed SkillGild tools; executable creator code is not uploaded to our servers.
- Import from GitHub: provide
https://github.com/owner/repository, an optional skill directory and an optional branch, tag or commit. Public repositories need no credentials. The converter resolves an immutable commit and copies supported text files into a hybrid draft. - Upload skill files: provide
SKILL.md, its text references and required license notices. For nested files, upload one JSON file whose keys are relative paths and whose values are file contents. The limit is 64 files and a 256 KiB assembled guide. Scripts and binary assets require separate review; a text import cannot make them hosted server tools.
Confirm that you are the author or have redistribution permission. Required copyright and license notices are preserved. Public author credit links to your SkillGild creator profile. The source repository, commit and conversion report are stored privately for review; GitHub is not required as your public author identity.
Conversion packages instructions; it does not guarantee that every upstream dependency works. Review warnings for missing assets, local scripts, mutable instruction URLs, external services and recurring actions before submitting. A missing or unclear license needs explicit review or redistribution authorization. Imported versions cannot publish until an operator records a conversion review.
#Private repositories and GitHub connection
Connect GitHub, authorize the SkillGild repository app, and grant read-only access to selected repositories. This is separate from signing in with GitHub. Use Grant repository access to install or update the app, then choose an authorized repository. Tokens are encrypted at rest, refreshed when needed and never included in guides. Disconnecting removes SkillGild's stored connection; revoke the app on GitHub to revoke its authorization there too.
If repository connection has not been configured on the deployment, public imports and uploads still work. A private upload needs no GitHub connection. Published guides are stored by SkillGild, so delivery does not require continued source access. A skill's external API may still be required for its workflow.
#Upstream updates
For a GitHub import, enable Check daily for updates and create a review draft. After publication, the worker checks the selected branch or reference. A changed commit creates a new draft with fresh provenance and review requirements. It never replaces the published guide automatically and never overwrites an existing draft. A fixed commit reference stays fixed. Private updates require a valid repository connection. For uploaded bundles, create a new version and use Replace this draft from source to upload a fresh JSON text bundle. The same action can reimport a GitHub snapshot into an editable draft; it clears selected tools and conversion review, and never edits a published version.
#Configure and submit
Save the agent guide, optionally select approved server tools, and upload the required demo media: one video with a poster and three images. Use authentic outputs and disclose illustrative fixtures.
#Review the page copy and FAQs
Saving or importing a guide automatically prepares a page draft for that version. Review your skill page in Creator Studio includes a search title, search description, overview, capabilities, good-fit tasks, limitations, requirements, example requests and FAQs. Edit the fields, preview the page, save changes and select I approve this page before submitting. Drafts are private and never replace the live listing on their own.
When configured, the platform's submission-review model receives the listing, guide and approved tool names to prepare copy. It does not execute the guide or follow its links. Remove credentials and private data that do not belong in a listing before saving a guide. If generation is unavailable or returns invalid content, a clearly labeled source-summary draft is provided for you to complete. Check every factual claim; generation does not establish that a capability works or guarantee search rankings.
Approval applies to the saved content revision and current guide, tools, listing and tier. Changing those inputs or regenerating the page clears approval. Source-update drafts require fresh approval. Editing page copy also requires saving and approving it again. During review, the team can inspect the exact approved page, request changes or publish it together with the version. Existing published pages retain their reviewed copy; future creator submissions use this approval flow.
Submit the draft. Automated checks inspect the listing, guide, media, safety, links and samples for any selected tools. The team reviews quality, rights, external instructions and tier. A requested Pro skill must have paid access and Pro-plan inclusion configured before initial approval. Published versions are immutable; updates use new drafts.
Guides are readable by the user's agent and can be retained. SkillGild controls hosted access and server-tool sessions; it cannot erase delivered instructions or measure offline reuse. The user's agent supplies the model. SkillGild does not fund inference for hybrid sessions.
#Creator revenue terms
Terms version: 2026-10-31-v1. The agreed split is 60% to eligible creators and 40% to SkillGild. The earning start timestamp and your enrollment status are shown in Creator Studio. No revenue-share earnings accrue before program activation, acceptance of these terms and approval of your creator's earning eligibility. Free skills do not earn this Pro usage share. Affiliate commissions remain a separate program.
#Revenue basis
Net revenue means actual verified subscription receipts less taxes, refunds, payment processing fees and applicable affiliate commissions. SkillGild pays its hosting, staff, support and other operating costs from its 40%; these general costs are not additional deductions from the creator pool. Each receipt's deductions must be reconciled before monthly allocation. Actual discounted receipts are used, not advertised list prices. Grants and unpaid access do not generate revenue.
Receipts are allocated over their paid service period using elapsed time in UTC. Annual and quarterly payments are spread across the calendar months they cover. The portion before program activation is excluded. Amounts stay in their original currency; different currencies are not silently converted or added together.
#Member-specific allocation
Each member's monthly creator allocation is 60% of the eligible net revenue for their covered service time. Divide that allocation among the eligible Pro skills accessed through SkillGild, in proportion to distinct member–skill–UTC days.
- One skill accessed 100 times on one UTC day counts once.
- Three different Pro skills accessed on the same day count once each, even if they share a creator.
- Free skills, self-usage, excluded artificial activity, background heartbeats and failed guide delivery do not qualify.
- Only approved, enrolled creators participate. SkillGild-owned and unclaimed listings are not enrolled by default. Their access does not dilute participating creators' shares.
- Local reuse of a delivered guide and direct activity on a creator's service cannot be observed and do not count as additional usage-days.
- If a member uses no eligible Pro skills, the unallocated amount stays with SkillGild; it is not redistributed to unrelated creators.
- Duplicate or artificially split listings may be excluded during review. Use
usage_context=backgroundfor automated background session requests; tools do not independently create usage-days.
Example: a member contributes $9 of eligible net revenue. The creator allocation is $5.40. If that member accesses creator C1's two skills on 5 and 2 days, C2's skill on 7 days, C4's on 1 day and C7's on 10 days, there are 25 skill-days. C1 receives $1.512, C2 $1.512, C4 $0.216 and C7 $2.16. Overlapping calendar days do not change this calculation. SkillGild retains $3.60 before its operating expenses.
#Accounting and manual settlement
Accept the terms in Creator earnings to request enrollment. The team verifies author rights and earning eligibility. Monthly draft allocations are estimates; an operator reconciles deductions and finalizes closed months. Finalized earnings have a 30-day hold after finalization (or month end, whichever is later). There is no automatic bank transfer. Settlement is manual, with an amount, currency, earning period and unique bank/provider reference recorded for reconciliation. Save your payment destination under Creator earnings. Details are encrypted and only opened by authorized payout operators, with each view audited. Verify the destination with the team before settlement; never put bank credentials in a skill guide or repository.
Amounts retain fractional minor units internally; payouts use whole minor units, with fractions carried forward. No minimum payout is enforced by this initial ledger. A verified refund or lost chargeback conservatively reverses the affected receipt's full creator allocation. If it was already paid, the resulting negative balance offsets future earnings. Repeated payment events and payout references cannot create duplicate earnings or payouts. Suspended or ineligible creators cannot receive new payout records until reviewed.
Authorship changes do not redirect historical usage: each qualifying access snapshots its creator. Any transfer and treatment of historical earnings must be reviewed by the team. Terms changes require a new version and explicit acceptance; the current implementation fixes the creator pool at 60%.
#Creator API
Creator endpoints use your signed-in session token, not a runtime API key. The Studio obtains one from /api/auth/token.
| Action | Endpoint |
|---|---|
| List your skills | GET /v1/me/creator/studio |
| Create a draft | POST /v1/me/creator/skills |
| Import a draft | POST /v1/me/creator/import |
| List versions | GET /v1/me/creator/skills/{skill}/versions |
| New version | POST /v1/me/creator/skills/{skill}/versions |
| Read/edit draft guide | GET / PUT /v1/me/creator/skills/{skill}/versions/{version}/runtime-config |
| Reimport into an editable draft | POST /v1/me/creator/skills/{skill}/versions/{version}/import |
| Read/edit the page draft | GET / PUT /v1/me/creator/skills/{skill}/versions/{version}/page-draft |
| Generate a new page draft | POST /v1/me/creator/skills/{skill}/versions/{version}/page-draft/generate |
| Approve saved page copy | POST /v1/me/creator/skills/{skill}/versions/{version}/page-draft/approve |
| Submit | POST /v1/me/creator/skills/{skill}/submit |
| Earnings and status | GET /v1/me/creator/earnings |
| Accept revenue terms | POST /v1/me/creator/revenue-terms |
| Repository connection status | GET /v1/me/creator/github |
| Start repository authorization | POST /v1/me/creator/github/connect |
| Authorized repositories | GET /v1/me/creator/github/repositories |
| Disconnect | DELETE /v1/me/creator/github |
Page edits send {"revision": 2, "content": {...}}; approval sends {"revision": 3} using the current returned revision. A stale revision or changed source returns a conflict. Generate again when source changes. Generation is limited to five manual requests per hour per creator, in addition to drafts queued when source changes.
Save a guide-only draft:
{ "agent_guide": "Your complete instructions...", "tools": [] }Import a public repository:
{
"slug": "my-skill",
"name": "My skill",
"description": "Describe what this skill does in at least twenty characters.",
"requested_access_tier": "paid",
"rights_confirmed": true,
"auto_sync": true,
"source": {
"repository": "https://github.com/owner/repository",
"path": "skills/my-skill",
"ref": "main"
}
}Add "use_github_connection": true for authorized private repositories. Import returns skill and report; it never publishes. To accept earning terms, send {"terms_version":"2026-10-31-v1"} to the terms endpoint.
Existing legacy prompt-pipeline API support, when deployment-enabled, is separate from this hybrid publishing flow. Creators cannot upload arbitrary server executable code.