agentleFS
Sign inStart free
WireCatLabsWireCatLabs/cli-docs/skills/blog-tags/SKILL.md

blog-tags

Skill1 starsChanged 5 days agoApache-2.0View on GitHub

Choose tags for a wirecat.dev blog post from the tag registry, or add a tag when none fits. Use when writing, translating or reviewing a post in cli-docs content/blog.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 1 is distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run pnpm blog:tags in the cli-docs checkout.

    line 9
  2. Distinctive:

    Write the id, never an alias or a label.

    line 13
  3. Very specific:

    Add a tag only when none of the descriptions fits.

    line 15
  4. Very specific:

    Run pnpm exec vitest run scripts/blog-tags.test.ts to check the registry and every post.

    line 21
  5. Very specific:

    Never rename or delete an id that posts use: tag pages are public URLs (/{lang}/blog/tags/{id}).

    line 23

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

Tags exist only in content/blog/tags.json. A post lists tag ids in its front matter (tags: [ai-agents, cli]); every language version of a post uses the same ids.

  1. Run pnpm blog:tags in the cli-docs checkout. It prints every id, how many posts use it, its label, description and aliases.
  2. Choose 2 to 4 ids whose descriptions match what the post is mostly about. Prefer a tag that already has posts over a narrower new one.
  3. Write the id, never an alias or a label. The build fails on an unknown id and on an alias; the error names the id to use.
  4. Add a tag only when none of the descriptions fits. First search the labels and aliases for your word and its synonyms. Then add one entry to tags.json in the same pull request as the post:
    • id: lowercase words joined by hyphens, the plain common name (search, not search-stuff).
    • label and a one-line description in English, Russian and Spanish.
    • aliases: the other spellings a writer might reach for (plural, abbreviation, product name). An alias or a label may belong to one tag only; the build fails otherwise.
  5. Run pnpm exec vitest run scripts/blog-tags.test.ts to check the registry and every post.

Never rename or delete an id that posts use: tag pages are public URLs (/{lang}/blog/tags/{id}). Merge two tags by keeping one id and moving the other id into its aliases, then update the posts.

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.

Check your setup, free