agentleFS
Sign inStart free
fleetdmfleetdm/fleet/.claude/skills/fleet-guide-formatting/SKILL.md

fleet-guide-formatting

Skill7.1k starsChanged 7 months agoLicence not identifiedView on GitHub

Ensure Fleet how-to guides (articles/ with meta category "guides") follow the concise, step-by-step structure established by Fleet's best guides: short problem statement, prerequisites, inline gotcha callouts, task-based or numbered steps, optional verify/troubleshoot sections, no filler. Use when writing a new guide, converting a draft into a guide, or auditing/retrofitting an existing guide's structure. Trigger on requests like "write a guide for X", "format this as a guide", "check guide formatting", "audit our guides", "does this follow our guide structure", or when editing a file under articles/ tagged category "guides". This skill governs STRUCTURE: what sections exist, in what order, how steps are shown. It does NOT replace the content-style skill. Always run content-style over the prose as part of using this skill, in the same session, before calling a guide done. Do NOT use this for articles, case studies, or announcements, which are different meta categories with their own conventions (articles use the fleet-article-formatting skill). If the piece's meta category is anything other than "guides", this format does not apply. A strong signal this skill applies: the draft reads like an opinion piece, roundup, or narrative with no concrete steps an admin could follow. That's the exact anti-pattern this skill exists to catch.

We split this skill into the rules it gives an agent

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

  • 5

    Very specific

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

The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.

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

Trending

Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Aug 30: 0 new projectsWeek of Sep 6: 0 new projectsWeek of Sep 13: 0 new projectsWeek of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projects
Aug 2026Sep 2026Oct 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 0 in all, so this is a hint, not a trend.

Who's talking about fleetdm/fleet

The biggest 5 of 55 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 55

Talked about on GitHub, Hacker News, Bluesky and Stack Overflow (55 times).

On GitHub · 50

45 more on GitHub

On Hacker News · 2

On Stack Overflow · 1

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