Skip to main content
ClaudeWave
Skill1.3k repo starsupdated 3d ago

make-me-a-skill

Turn a task you repeat every week into a reusable personal skill or prompt — so you say 'do this' instead of re-explaining it every time. Use when asked help me make a skill for, turn this repetitive task into a template, I do this every week, or create a reusable prompt for this. Produces a captured spec of the repetitive task (its inputs, steps, and what good output looks like), a reusable skill/prompt you can invoke by name, and guidance on saving and refining it — lowering the barrier from AI user to AI author, one weekly task at a time.

Install in Claude Code
Copy
git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills /tmp/make-me-a-skill && cp -r /tmp/make-me-a-skill/exports/obsidian/pm-focus/make-me-a-skill/make-me-a- ~/.claude/skills/make-me-a-skill
Then start a new Claude Code session; the skill loads automatically.

make-me-a-skill.md

# Make Me a Skill

The biggest leverage in working with AI is turning your repeated tasks into reusable skills — so formatting the meeting notes, writing the weekly update, or organizing the tasks becomes "do the thing" instead of re-explaining it every time. This captures one such task into a clean, reusable skill or prompt you can invoke by name, and shows you how to save and improve it. Do it once and you'll do it for everything.

## What This Skill Produces

- **The captured task** — the repetitive thing, spelled out: what it takes in, the steps it follows, and what a good result looks like
- **A reusable skill/prompt** — a clean, named artifact you can invoke ("do my weekly update") instead of re-explaining
- **The output template** — the consistent format the skill should produce each time
- **Save & invoke guidance** — where to keep it (a skill file, a saved prompt, a snippet) and how to trigger it
- **A refine loop** — how to improve it as you use it (the first version is never the last)

## Required Inputs

Ask for these if not provided:
- **The repetitive task** — the thing you do regularly and re-explain each time
- **A good example** — one instance of the task done well (the target output)
- **The inputs it needs** — what information you feed it each time
- **Where you'll use it** — Claude Code, a chat, a specific tool (shapes the format)

## Framework: Capture, Templatize, Reuse

1. **Pick one repeated task.** Start with a single weekly thing — the highest-frequency, most-annoying-to-re-explain one.
2. **Extract the spec.** From how you currently do it (and a good example), capture the inputs, the steps, and what "good" looks like — the reusable essence.
3. **Write the invocable artifact.** Turn it into a named skill or prompt with a clear trigger, required inputs, and an output template — so next time it's one instruction.
4. **Fit the tool.** Format it for where it'll live (a SKILL.md, a saved prompt, a text snippet) and note how to invoke it.
5. **Refine as you go.** Treat v1 as a draft — each use surfaces a tweak. And once one exists, the pattern generalizes to your other repeated tasks.

## Output Format

### Skill: [name] — for [the repetitive task]

**What it does:** [one line].
**Inputs it needs:** [the info you feed it].
**The skill/prompt (reusable):**
> [The invocable instruction — trigger, steps, and the output template it should follow.]

**Save it as:** [SKILL.md / saved prompt / snippet], invoke with "[trigger phrase]".
**Refine it:** each time you use it, tweak the part that wasn't quite right. Then make one for your next repeated task.

## Quality Checks
- [ ] Captures a genuinely repeated task's inputs, steps, and good-output
- [ ] Produces a reusable, invocable skill/prompt with a clear trigger
- [ ] Includes a consistent output template
- [ ] Gives concrete save-and-invoke guidance for the person's tool
- [ ] Includes a refine loop and the generalize-to-others nudge

## Anti-Patterns
- **A one-off answer** instead of a reusable artifact.
- **Capturing a vague task** with no clear inputs or output.
- **No trigger/invocation** guidance.
- **Treating v1 as final** with no refine loop.

## Example Trigger Phrases
- "I format meeting notes the same way every week — make me a skill for it."
- "Turn my weekly status update into a reusable prompt."
- "Help me create a template skill for organizing my tasks."
- "I keep re-explaining this to AI — capture it as a skill."
- "Make a 'do this' skill out of my monthly report process."

---
<!-- Run as an AI-plugin prompt. {{selection}} is the Text Generator / Templater
     variable for the highlighted text — replace it with your plugin's equivalent
     (e.g. {} in Copilot for Obsidian), or paste your input there manually. -->
Apply the skill above to the following input:

{{selection}}
ai-ethics-reviewSkill

Conduct a structured ethical review of an AI or ML feature, model, or product. Use when preparing to deploy an AI system, assessing algorithmic risk, auditing a model for bias, or producing a responsible AI impact assessment. Produces a structured ethics review covering fairness, transparency, privacy, safety, accountability, and societal impact with a risk tier score, pre-deployment checklist, and prioritised mitigations.

ai-product-canvasSkill

Structure AI and ML product decisions with the rigour of any product decision. Use when building AI-powered features, evaluating LLM integrations, designing AI products, or assessing AI readiness. Produces a complete AI product canvas covering problem definition, model approach, data requirements, evaluation framework, UX design, responsible AI checklist, and launch monitoring plan.

design-handoff-briefSkill

Transform feature briefs into structured design briefs that give designers the context they need before opening Figma. Use when asked to write a design brief, create a design handoff, brief a designer on a new feature, or translate a PRD into design requirements. Produces a brief with user goal, emotional context, success criteria, constraints, edge cases, and out-of-scope boundaries.

experiment-designerSkill

Design statistically rigorous A/B tests and interpret experiment results. Use when asked to design an experiment, run an A/B test, calculate sample size, interpret test results, or assess whether an experiment was successful. Produces a complete experiment design with hypothesis, sample size, run time, success criteria, and risk flags — or a results interpretation with ship/iterate/kill recommendation.

multi-source-signal-synthesiserSkill

Synthesises user signals from multiple research sources into a unified, weighted insight brief. Use when you have data from interviews, support tickets, NPS verbatims, app reviews, or sales calls and need to reconcile contradictions, surface the underlying need behind requests, or answer 'what are users really telling us'. Produces ranked insights with confidence ratings, source weighting rationale, divergent signal analysis by user segment, and a research gap identification section.

data-analysis-standardSkill

Structure a product data analysis, metric deep-dive, funnel analysis, or cohort study. Use when asked to analyse product metrics, investigate a drop in conversion, explain a data change to stakeholders, or find the root cause of a metric movement. Produces a structured analysis with question, root cause, confidence level, and recommended action.

product-health-analysisSkill

Interpret product metrics against goals and surface actionable signals. Use when asked to analyse product health, review key metrics, investigate a performance issue, produce a health report, or assess product-market fit signals. Produces a structured health report with RAG status, trend analysis, root cause hypotheses, and prioritised actions.

retention-analysisSkill

Structure a retention analysis, churn investigation, or engagement deep-dive for any product team. Use when asked to analyse user retention, investigate churn, measure DAU/MAU, or build a retention improvement plan. Produces a retention snapshot with root cause hypotheses, aha-moment correlation, and prioritised interventions.