agentleFS
portolan-sdiportolan-sdi/portolan-skills/skills/register-catalog/SKILL.md

register-catalog

Skill11 starsChanged 32 days agoApache-2.0View on GitHub

Submit a Portolan catalog to the registry by following the registry README.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 6 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read the current registry README and find the submission instructions.

    line 10
  2. Distinctive:

    Follow them for the user's catalog, including linked validation guidance and contribution requirements.

    line 11
  3. Distinctive:

    Use the user's preferred submission method.

    line 12
  4. Distinctive:

    Ask for required information the user has not supplied.

    line 14
  5. Distinctive:

    Never guess the submitter email address or read it from git config.

    line 15
  6. Distinctive:

    If blocked, report what the user needs to provide or fix.

    line 18

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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
<!-- drift: depends-on: portolan-registry -->

Register a catalog in the Portolan registry

Read the current registry README and find the submission instructions. Follow them for the user's catalog, including linked validation guidance and contribution requirements. Use the user's preferred submission method.

Ask for required information the user has not supplied. Never guess the submitter email address or read it from git config.

Complete the submission and return its URL. If blocked, report what the user needs to provide or fix.

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.