agentleFS
Sign inStart free
BlakeemBlakeem/aipromptguide-workflows/skills/docs/SKILL.md

docs

Skill1 starsChanged 8 days agoMITView on GitHub

Run the AIPG docs workflow, which copies the docs a project builds against verbatim from the web, repos or local files. It then scrubs the captured web pages and curates and indexes the set into a working folder. Use only when the user explicitly asks for the AIPG docs workflow.

165 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 9 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

We split this skill into the rules it gives an agent

3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 129 edited versions we read keep these.

  • 1

    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. Very specific:

    When plugin-access.mjs exits 1, show the user its message, which names the cause, and run it again once the cause is fixed.

    line 13
  2. Very specific:

    Read ${CLAUDE_PLUGIN_ROOT}/workflows/docs/CLAUDE.md and follow it exactly.

    line 16
  3. Distinctive:

    Use these paths wherever the guide says "this checkout" or "the tool's own directory":

    line 18

“Common” is measured: kept by at least 6 in 10 of the 129 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

The user wants to run the docs-cycle dynamic workflow on the brief below.

First run node "${CLAUDE_PLUGIN_ROOT}/tools/plugin-access.mjs" check. The Workflow tool launches only engines the session can read. On missing, unless the working directory is ${CLAUDE_PLUGIN_ROOT} or a folder above it, ask the user once whether to add the printed Read rule to their user settings. On yes, run the command again with grant (settings reload live, no restart). On no, the user can run /add-dir ${CLAUDE_PLUGIN_ROOT} for this session only. When plugin-access.mjs exits 1, show the user its message, which names the cause, and run it again once the cause is fixed.

Read ${CLAUDE_PLUGIN_ROOT}/workflows/docs/CLAUDE.md and follow it exactly. Work its ## 0. Checklist top to bottom. Use these paths wherever the guide says "this checkout" or "the tool's own directory":

  • Engine scriptPath: ${CLAUDE_PLUGIN_ROOT}/workflows/docs/docs-cycle.mjs
  • root arg: ${CLAUDE_PLUGIN_DATA}. Runs land in its runs/<runId>/. Never the plugin install dir, which is version-swapped on update.
  • outDir is where the user wants the doc set, usually inside their project.

$ARGUMENTS

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