find-prompt

Solid

Use when the user names a coding or Claude Code task ("add OAuth", "set up hooks", "review this PR", "pick a model"), asks which prompt to use, says to "use the right prompt", or when you enter this repo and need to orient without reading every file.

AI & Automation 51 stars 15 forks Updated 6 days ago MIT

Install

View on GitHub

Quality Score: 87/100

Stars 20%
57
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Find the right prompt and run with it You route the current task to the right file(s) in this library, **read them yourself**, and then **continue the existing work** under those instructions — not from scratch, but picking up the conversation and any task already in progress. `${CLAUDE_SKILL_DIR}` is this skill's own directory (`<library-root>/.claude/skills/find-prompt/`). The library root is `${CLAUDE_SKILL_DIR}/../../..`. All prompt files are under `${CLAUDE_SKILL_DIR}/../../../prompts/english/`. Never hardcode an absolute path — always build it from `${CLAUDE_SKILL_DIR}` so this works for anyone who clones the library, wherever they put it. If `${CLAUDE_SKILL_DIR}` is not substituted (it shows up literally), fall back: the skill sits next to `SKILL.md`; run `ls` up the tree from your working directory to find the folder containing `prompts/english/agents/claude-agent-system-prompt.md`. ## Steps 1. **Determine the task.** Use `$ARGUMENTS` if given. Otherwise use the task already being worked on in this conversation (the user's last real request, the in-progress work, the files open). If genuinely unclear, ask one short question and stop. 2. **Match the task** to the routing table below. Pick the **base** prompt plus specialists by tier: 1 for a single-domain task (default), 2 only if the task spans two genuinely independent domains, or route to Multi-Agent Orchestration if the work needs isolation/review. See `${CLAUDE_SKILL_DIR}/../../../prompts/english/workflows...

Details

Author
Rtur2003
Repository
Rtur2003/Claude-Code-Promts-Skills
Created
8 months ago
Last Updated
6 days ago
Language
Python
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

prompt-engineering

This skill should be used when the user says "write a prompt", "prompt engineering", "system prompt", "optimize my prompt", "create instructions for", "context engineering", "CLAUDE.md", "few-shot examples", "write me a Midjourney prompt", "create a GPT prompt", "prompt for Claude Code", "agentic prompt", "tool description", or needs to create, improve, or optimize prompts for any AI platform. Covers prompt writing, system prompts, tool descriptions, agentic workflows, prompt chaining, and cross-model migration. Use for any prompt-related task, even simple ones.

5 Updated 3 weeks ago
RadOrigin-LLC
AI & Automation Listed

prompt-craft

Writing, improving, and auditing prompts for LLMs (Claude 4.x/5, GPT-5.x, Gemini 3, Perplexity Sonar and similar) according to modern prompt- and context-engineering practice of 2025–2026. Use this skill whenever the user asks to "write a prompt", "draft a prompt", "make a system prompt", "a prompt for an agent", "a prompt for GPT/Claude/Gemini/Perplexity", "improve my prompt", "rewrite this prompt", "make it jailbreak-resistant", "protect the prompt from injection", "write instructions for a model", "prompt template", "few-shot examples", "system prompt", "configure reasoning/thinking", "why does the model ignore my instructions", or when the user hands over a raw task meant for another model and wants a polished instruction back. Trigger even if the word "prompt" is never said — if the user is preparing an instruction to feed to another LLM system (a chatbot, an agent, a RAG pipeline, a classifier, an LLM judge), that is a prompt-craft task.

0 Updated 1 weeks ago
kravcovtech
AI & Automation Listed

promptify

Rewrite a rough, vague, or bloated prompt into a best-practices prompt for the Claude model in use, grounded in the current repo (real file paths, existing patterns, the test/build command that proves the change, CLAUDE.md conventions). Use when the user says "upgrade/improve/optimize/rewrite my prompt", "make this a better prompt", "how should I ask for this", "promptify", or pastes a task and wants it phrased properly before running it. Produces the prompt; runs it only with --run.

0 Updated 1 weeks ago
tahabozdemir