agentleFS
Sign inStart free
mrieckmrieck/seoblog-claude-plugin/skills/seoblog-setup/SKILL.md

seoblog-setup

Skill0 starsChanged 53 days agoMITView on GitHub

Configure or edit an SEO Blog site, voice (tone guide and voice samples), CMS connection, and optional images.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read runtime instructions before running scripts.

    line 8
  2. Distinctive:

    Use the seo-blog skill's *Setup interview* section to fulfil this request.

    line 10
  3. Distinctive:

    Use the user’s request as the arguments.

    line 12
  4. Very specific:

    Write the config to ~/.config/seoblog/config.json (non-secret — never put API keys in it).

    line 18
  5. Very specific:

    Verify with node "${SEOBLOG_PLUGIN_ROOT}/scripts/doctor.mjs" --site <id> and walk through fixing anything that fails.

    line 24

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

Set up SEO Blog

Read runtime instructions before running scripts.

Use the seo-blog skill's Setup interview section to fulfil this request.

Use the user’s request as the arguments.

  1. Interview the user (AskUserQuestion) for: site id, baseUrl, cmsType, author, niche, tone, optional voice samples (1–3 paragraphs of their own writing, inline or as file paths, saved as voiceSamples), default article length, optional product, optional standing directions.
  2. Write the config to ~/.config/seoblog/config.json (non-secret — never put API keys in it). Set defaultSite if it's the first site.
  3. On macOS, print the exact security add-generic-password commands for the user to run themselves in their own terminal — never accept a key pasted into the chat, and never write one from a tool call. On other systems, use the environment-variable instructions in the runtime guide.
  4. Verify with node "${SEOBLOG_PLUGIN_ROOT}/scripts/doctor.mjs" --site <id> and walk through fixing anything that fails.

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