agentleFS
Sign inStart free
everpcpceverpcpc/KMReader/.agents/skills/docs/SKILL.md

docs

Skill118 starsChanged 7 days agoMITView on GitHub

Regenerate README.md, APP_STORE_DESCRIPTION.txt, and the KMReader landing page (src/pages/reader/index.tsx in the kmworks/website repo) based on current important product features in the codebase.

169 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use import-memory, perf and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • amirbironSkill

    import-memory

    Import a memory export from another AI assistant into Claude's memory — conversationally, additively, and with the content treated as data.

    Also in 3 projects that use this

  • MicrosoftSkill

    perf

    Speed and memory performance rules for Rust crates, the Node addon, webui-framework, and webui-delivery.

    Also in 4 projects that use this

  • diego-tobalinaSkill

    build-fix

    Fix build and compilation errors systematically. Run when build fails.

    Also in 3 projects that use this

  • JkudjoSkill

    incident

    Production incident response — structured triage, hypothesis tree, safe remediation, incident record

    Also in 4 projects that use this

  • vbrevikSkill

    work

    Use when the user says 'plan', 'todo', 'copy plan', 'append plan', 'resume plan', 'priorities', or 'what's next'.

    Also in 7 projects that use this

  • mbwsimsSkill

    impact

    This skill should be used when the user asks to "check the impact", "what will break if I change this", "blast radius", "impact analysis", "what depends on this", "who imports this", "is it safe to change this", mentions "/impact", or wants to understand the consequences of modifying a specific file or function before making changes.

    Also in 3 projects that use this

The file

Show its rules and text

We split this skill into the rules it gives an agent

13 rules. 0 are common, 11 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 133 edited versions we read keep these.

  • 11

    Distinctive

    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:

    Treat docs as a durable product overview, not a summary of every recent change.

    line 25
  2. Distinctive:

    Do not add minor UX polish, small fixes, or short-lived release-specific details unless they change the core product positioning.

    line 26
  3. Distinctive:

    Keep product-facing language clear and concise.

    line 27
  4. Distinctive:

    Avoid low-level technical implementation details.

    line 28
  5. Distinctive:

    Keep messaging consistent across all three files.

    line 29
  6. Distinctive:

    Keep any supported-language claims aligned with the current app localization set.

    line 30
  7. Distinctive:

    Update all target files so wording and feature emphasis stay aligned.

    line 43
  8. Distinctive:

    Keep README.md as the most complete overview.

    line 44
  9. Very specific:

    Keep APP_STORE_DESCRIPTION.txt concise and store-appropriate.

    line 45
  10. Very specific:

    Keep the website repo's src/pages/reader/index.tsx aligned with the same feature priorities.

    line 46
  11. Distinctive:

    Ensure all three files mention the same core features.

    line 50
  12. Distinctive:

    Remove stale or no-longer-available claims.

    line 51
  13. Distinctive:

    Keep formatting clean and ready to publish.

    line 52

“Common” is measured: kept by at least 6 in 10 of the 133 edited versions of this file we could read. “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

Docs

Regenerate key project docs from current product capabilities.

When To Use

  • The user asks to refresh project docs after feature changes.
  • README and App Store description are outdated.
  • Marketing landing content in the kmworks/website repo (src/pages/reader/index.tsx) needs alignment with current app features.

Target Files

  • README.md
  • APP_STORE_DESCRIPTION.txt
  • src/pages/reader/index.tsx in the kmworks/website repo (commit there separately)

Scope Rules

  • Reflect current important features only.
  • Treat docs as a durable product overview, not a summary of every recent change.
  • Do not add minor UX polish, small fixes, or short-lived release-specific details unless they change the core product positioning.
  • Keep product-facing language clear and concise.
  • Avoid low-level technical implementation details.
  • Keep messaging consistent across all three files.
  • Keep any supported-language claims aligned with the current app localization set.

Inputs To Read First

  • AGENTS.md (project capabilities and architecture summary) and .agents/skills/repo-conventions/SKILL.md (subsystem conventions)
  • Current target files (to preserve structure where appropriate)
  • Relevant feature modules under KMReader/Features/ when needed

Update Workflow

  1. Collect current user-visible features from codebase and project docs.
  2. Decide the most important feature set to present.
  3. Filter out low-signal recent changes that belong in changelogs rather than evergreen docs.
  4. Update all target files so wording and feature emphasis stay aligned.
  5. Keep README.md as the most complete overview.
  6. Keep APP_STORE_DESCRIPTION.txt concise and store-appropriate.
  7. Keep the website repo's src/pages/reader/index.tsx aligned with the same feature priorities.

Validation

  • Ensure all three files mention the same core features.
  • Remove stale or no-longer-available claims.
  • Keep formatting clean and ready to publish.

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