agentleFS
IgorGanapolskyIgorGanapolsky/mac-yolo-safeguards/.agents/skills/github-marketplace-action-publish/SKILL.md

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

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
  1. Very specific:

    If counsel_clearance is not true: free OSS listing of the existing Action is allowed.

    line 51
  2. Distinctive:

    If already LIVE at expected slug + version, stop (or ship a new tag only).

    line 64
  3. Distinctive:

    Check Publish this Action to the GitHub Marketplace

    line 80

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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)
  • gh auth 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)

FieldValue
RepoIgorGanapolsky/ThumbGate
Slugthumbgate-agent-governance (from action.yml name)
Listinghttps://github.com/marketplace/actions/thumbgate-agent-governance
CategoriesPrimary Security, optional AI Assisted
Installuses: IgorGanapolsky/ThumbGate@v1 or @v1.35.2
CommercialFree 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

  1. Probe first (prefer fleet copy in this repo):
    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
    If already LIVE at expected slug + version, stop (or ship a new tag only).
  2. Tag + release (CLI, no Marketplace checkbox):
    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"
    Point floating major tag at the same commit:
    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
  3. 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
  4. Sudo wall: Gmail OTP → /gmail-auth-fix if revoked. Do not invent "blocked"; tagged uses: remains the working rail.
  5. 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

FieldSource
LIVE URLverify script listing URL + HTTP 200
uses:Marketplace dialog or OWNER/REPO@tag
Versionrelease tag + floating v1 SHA
ECIfree-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

NEVERALWAYS
Treat gh release create as Marketplace publishProbe listing before tagging
Guess the slugDerive from action.yml name, confirm HTTP 200
Claim search "0 results" without fetching the expected URLFetch listing URL + search
Paid plans without counsel clearanceFree listing only while counsel_clearance is false
Igor's daily ChromeBrowserOS neo
LIVE without verify exit 0/verify-github-marketplace-listing

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.