agentleFS
limyuquanlimyuquan/planner/skills/link-plan/SKILL.md

link-plan

Skill1 starsChanged 37 days agoMITView on GitHub

Show the user a markdown or HTML plan in Planner instead of giving them a file path. Use whenever you point the user at a plan, recap, ELI5, explainer, or any other doc in the docs folder.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 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.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use the port from the user's dashboard if it is not the default 4173.

    line 31

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

link-plan

Send the doc to the dashboard tab the user already has open — a clicked link would open yet another tab:

planner open '<url>'

It starts the dashboard if it is down, and opens a tab only when no dashboard is running. Put the same URL in your message too, so it can be reopened later.

Files sitting directly in a phase folder, a task's plans folder, or an extra folder like research/ are named by workspace and file name, never by title. Leave out the status folder (active/, done/) and the plans folder, so the link survives the task being settled:

http://localhost:4173/?ws=<task-folder>[/<phase-folder>]&plan=<file>
http://localhost:4173/?ws=search-rewrite/phase-2-query-api&plan=plan.md
http://localhost:4173/?ws=search-rewrite&plan=mother-plan.html

Anything else is not listed in the sidebar, so name it by its path under the docs folder (or its absolute path):

http://localhost:4173/?doc=<path-under-the-docs-folder>
http://localhost:4173/?doc=notes/meeting-2026-01-12.md

Use the port from the user's dashboard if it is not the default 4173.

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.