agentleFS
IgorGanapolskyIgorGanapolsky/mac-yolo-safeguards/.agents/skills/advertise-thumbgate-github-marketplace/SKILL.md

advertise-thumbgate-github-marketplace

Skill3 starsChanged 4 days agoMITView on GitHub

Cite the live GitHub Marketplace Action listing when advertising ThumbGate (free listing only). Trigger: advertise ThumbGate on Marketplace, listing badge, uses: snippet for README, Marketplace install URL, Action discovery. Slash: /advertise-thumbgate-github-marketplace. Never claim LIVE without /verify-github-marketplace-listing. Never paid plans or buyer outreach without /eci-thumbgate-ip-wall clearance.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 2 are distinctive, and 3 are 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.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Verify script exit 0 this turn (no cached "we published yesterday")

    line 29
  2. Very specific:

    Run /verify-github-marketplace-listing (--json).

    line 35
  3. Very specific:

    Read counsel_clearance. If false: free listing cite only.

    line 36
  4. Distinctive:

    Do not add $499, Partner Pilot, enterprise hardening, or "book a call" onto this surface while counsel is uncleared.

    line 47
  5. Very specific:

    Verify script live=true and listing.http=200 in the same turn.

    line 52

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

Advertise ThumbGate via GitHub Marketplace (free listing)

This is the cite-the-listing skill, not the publish skill and not paid GTM. Marketplace is a discovery surface for the existing public Action. It is not a paid-pilot channel.

Chain: /verify-github-marketplace-listing (must exit 0) → this skill. Publish/update the listing: /github-marketplace-action-publish. ECI wall: /eci-thumbgate-ip-wall.

When to use

User wants to advertise ThumbGate on / via GitHub Marketplace, drop a listing URL into a README or promo draft, or needs the uses: snippet.

Required inputs + access

  • Verify script exit 0 this turn (no cached "we published yesterday")
  • counsel_clearance from ~/.thumbgate/private-legal/eci-employment/STATUS.json
  • Allowed copy: listing URL + uses: + categories already on the listing

Sequence

  1. Run /verify-github-marketplace-listing (--json). Stop if not live.
  2. Read counsel_clearance. If false: free listing cite only.
  3. Return only evidence-backed fields from the verify JSON.

Allowed cite (after LIVE):

Action: https://github.com/marketplace/actions/thumbgate-agent-governance
Install: uses: IgorGanapolsky/ThumbGate@v1
Categories: Security, AI Assisted

Do not add $499, Partner Pilot, enterprise hardening, or "book a call" onto this surface while counsel is uncleared.

How to validate

Verify script live=true and listing.http=200 in the same turn. Stale vault notes are not evidence.

What to return

FieldSource
Listing URLlisting.url
Titlelisting.title
uses:listing.uses or @v1
ECIfree-cite-only vs paid-paused

What requires approval

  • Paid Marketplace plans
  • Buyer / pilot / enterprise outreach that uses the listing as a lead magnet
  • Expanding listing claims beyond the existing Action description

NEVER / ALWAYS

NEVERALWAYS
Advertise a 404 or guessed slugVerify this turn
Paid plans / pilot CTAs on the listingFree uses: + URL only
Invent install badges without LIVEQuote verify JSON
Hijack Igor's Chrome to "screenshot the listing"HTTPS verify script

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.