github-marketplace-action-publish
Skill3 starsChanged 4 days agoMITView on GitHub
Publish or update a GitHub Actions listing on GitHub Marketplace (free only for ThumbGate until counsel clearance). Trigger: GitHub Marketplace, publish this Action, Draft a release, marketplace listing, advertise the action, uses: IgorGanapolsky/ThumbGate, action.yml branding. Slash: /github-marketplace-action-publish. Never claim LIVE without /verify-github-marketplace-listing. Never add paid Marketplace plans without /eci-thumbgate-ip-wall clearance.
- Commits and pushes
In this repository153 other files it gives its agents.
- AGENTS.mdAGENTS.md
- hermes-mobile/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- .cursor/rules/agent-automations.mdcCursor rule
- .cursor/rules/agent-device.mdcCursor rule
- .cursor/rules/agent-harness-router.mdcCursor rule
- .cursor/rules/agent-skills-overview.mdcCursor rule
- .cursor/rules/always-agent-mode.mdcCursor rule
- .cursor/rules/callstack-agent-skills-overview.mdcCursor rule
- .cursor/rules/callstack-react-native-best-practices.mdcCursor rule
- .cursor/rules/codeql-agent-hygiene.mdcCursor rule
- .cursor/rules/decision-stack.mdcCursor rule
- .cursor/rules/expo-credit-budget.mdcCursor rule
- .cursor/rules/fleet-repo-intelligence.mdcCursor rule
- .cursor/rules/hermes-mobile-prevention-july-2026.mdcCursor rule
- .cursor/rules/hermes-mobile-real-users.mdcCursor rule
- .cursor/rules/hermes-mobile-verification.mdcCursor rule
- .cursor/rules/no-desktop-hijack.mdcCursor rule
- .cursor/rules/no-manual-handoffs.mdcCursor rule
- .cursor/rules/obsidian-teammate-collaboration.mdcCursor rule
- .cursor/rules/prefer-headless-background-ops.mdcCursor rule
- .cursor/rules/react-native-best-practices.mdcCursor rule
- public/llms.txtllms.txt
- advertise-thumbgate-github-marketplaceSkill
- agent-harness-routerSkill
- agentic-pattern-selectorSkill
- agents-judgment-calls-gateSkill
- ai-native-sdlcSkill
- android-dev-summit-26-gateSkill
- anti-babysitting-mandateSkill
- anti-babysittingSkill
- background-agent-hold-gateSkill
- browseros-agent-harnessSkill
- webmcp-agent-readinessSkill
- ci-first-failSkill
- ci-pr-monitorSkill
- cloudflare-developer-stackSkill
- cloudflare-kitesurf-browserSkill
- cloudflare-monetization-gatewaySkill
- confidence-offer-gateSkill
- content-laneSkill
- context-six-blockSkill
- context-vaultSkill
- context-weight-gateSkill
- dual-model-agentic-graphragSkill
- egm-fresh-reviewSkill
- elevenlabs-voice-agentsSkill
- emeans-quant-and-instinctSkill
- explainx-trending-honestSkill
- explainx-trending-ragSkill
- future-agi-self-healing-engineSkill
- garryslist-opportunity-trackerSkill
- gemini-decisions-hold-gateSkill
- git-at-scaleSkill
- gitbutler-fleet-automationsSkill
- gitbutler-google-ssoSkill
- gitbutler-mcp-isolatedSkill
- gitbutler-session-absorbSkill
- git-hooks-no-huskySkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 51
If counsel_clearance is not true: free OSS listing of the existing Action is allowed.
- Distinctive: line 64
If already LIVE at expected slug + version, stop (or ship a new tag only).
- Distinctive: line 80
Check Publish this Action to the GitHub Marketplace
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Publish a GitHub Action to Marketplace
Marketplace publish is UI-only. gh release create ships tags; it does
not list the Action. BrowserOS neo on the release form is the publish rail.
Chain: /eci-thumbgate-ip-wall (ThumbGate) → this skill →
/verify-github-marketplace-listing. To cite the listing in promo, then
/advertise-thumbgate-github-marketplace.
When to use
User asks to publish / update / list a GitHub Action on Marketplace, or to "advertise the Action" via a listing that is not yet proven LIVE.
Required inputs + access
- Public repo with root
action.yml(name,description,branding.icon/color) ghauth for tags/releases- BrowserOS neo (not Igor's daily Chrome) for the Marketplace checkbox
- Gmail MCP / Hermes Gmail for GitHub sudo OTP (never print the code)
- ThumbGate:
~/.thumbgate/private-legal/eci-employment/STATUS.json
ThumbGate defaults (verified 2026-08-17)
| Field | Value |
| Repo | IgorGanapolsky/ThumbGate |
| Slug | thumbgate-agent-governance (from action.yml name) |
| Listing | https://github.com/marketplace/actions/thumbgate-agent-governance |
| Categories | Primary Security, optional AI Assisted |
| Install | uses: IgorGanapolsky/ThumbGate@v1 or @v1.35.2 |
| Commercial | Free listing only until counsel_clearance=true |
Repo banner "You can publish this Action" ≠ listed. Wrong-slug 404 is not
proof of absence — slugify action.yml name (spaces → hyphens, lowercased).
ECI (ThumbGate)
If counsel_clearance is not true: free OSS listing of the existing Action is
allowed; paid Marketplace plans, trials, enterprise-claim expansion, and
buyer/pilot outreach from the listing are forbidden. Full wall:
/eci-thumbgate-ip-wall. Do not paste employer agreement text here.
Sequence
- Probe first (prefer fleet copy in this repo):
If already LIVE at expected slug + version, stop (or ship a new tag only).node .agents/skills/github-marketplace-action-publish/scripts/verify-listing.js --json # any repo: node ~/.grok/skills/github-marketplace-action-publish/scripts/verify-listing.js --json - Tag + release (CLI, no Marketplace checkbox):
Point floating major tag at the same commit:gh release create vX.Y.Z --repo OWNER/REPO --target main \ --title "vX.Y.Z — GitHub Marketplace action" \ --notes "Free Action. uses: OWNER/REPO@vX.Y.Z"COMMIT=$(gh api repos/OWNER/REPO/git/ref/tags/vX.Y.Z --jq .object.sha) gh api -X POST repos/OWNER/REPO/git/refs -f ref=refs/tags/v1 -f sha="$COMMIT" \ || gh api -X PATCH repos/OWNER/REPO/git/refs/tags/v1 -f sha="$COMMIT" -F force=true - Publish checkbox via BrowserOS neo:
- Open
https://github.com/OWNER/REPO/releases/edit/vX.Y.Z - Disabled checkbox → accept GitHub Marketplace Developer Agreement → Accept Terms
- Check Publish this Action to the GitHub Marketplace
- Primary + optional second category → Update / Publish release
- Open
- Sudo wall: Gmail OTP →
/gmail-auth-fixif revoked. Do not invent "blocked"; taggeduses:remains the working rail. - Verify with
/verify-github-marketplace-listing. No LIVE claim without exit 0.
How to validate
Exit 0 from the verify script against the slug derived from action.yml name.
HTTP 200 + real <title> (not GitHub 404 page). Search lag is not a delist.
What to return
| Field | Source |
| LIVE URL | verify script listing URL + HTTP 200 |
uses: | Marketplace dialog or OWNER/REPO@tag |
| Version | release tag + floating v1 SHA |
| ECI | free-only vs paid-paused |
What requires approval
- Paid Marketplace pricing / trials
- Expanding enterprise claims on the listing
- Buyer/pilot outreach from the listing
- Anything that is not a free listing of the already-public Action
NEVER / ALWAYS
| NEVER | ALWAYS |
Treat gh release create as Marketplace publish | Probe listing before tagging |
| Guess the slug | Derive from action.yml name, confirm HTTP 200 |
| Claim search "0 results" without fetching the expected URL | Fetch listing URL + search |
| Paid plans without counsel clearance | Free listing only while counsel_clearance is false |
| Igor's daily Chrome | BrowserOS neo |
| LIVE without verify exit 0 | /verify-github-marketplace-listing |
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

