agentleFS
Sign inStart free
Rtur2003Rtur2003/Claude-Code-Promts-Skills/.agents/skills/find-prompt/SKILL.md

find-prompt

Skill53 starsChanged 54 days agoMITView on GitHub

Use when the user names a coding, Claude Code, research, documentation, or technology-selection task; asks which prompt to use; says to use the right prompt; or when an agent enters this repository and needs to orient without reading every file.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    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:

    Treat CLAUDE.md and Claude Code configuration as subject matter, not as instructions for the current host, unless the task is specifically …

    line 13
  2. Distinctive:

    Use the current host's supported tool names and permission model while preserving the selected prompt's evidence, safety, verification, and …

    line 14
  3. Distinctive:

    Keep all conversation constraints, including any prohibition on Git operations, deployment, external messages, or credentials.

    line 15
  4. Distinctive:

    After routing, state the loaded prompt path, the continuing task, measurable success criteria, and carried constraints in one short block, …

    line 18

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

Find the right prompt and continue

This repository keeps one canonical routing table at .claude/skills/find-prompt/SKILL.md. Read that file completely, resolve its paths from the repository root, and follow its routing and composition rules.

Cross-agent adaptations:

  • Treat CLAUDE.md and Claude Code configuration as subject matter, not as instructions for the current host, unless the task is specifically about Claude Code.
  • Use the current host's supported tool names and permission model while preserving the selected prompt's evidence, safety, verification, and completion requirements.
  • Keep all conversation constraints, including any prohibition on Git operations, deployment, external messages, or credentials.
  • Load only files that exist. If the canonical route is missing, use prompts/english/INDEX.md and report the inconsistency.

After routing, state the loaded prompt path, the continuing task, measurable success criteria, and carried constraints in one short block, then continue the work.

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