Interview Me
addyosmani/agent-skills
Asks one question at a time, each with a best guess attached, until the agent is about 95 percent sure what you really want, before any plan, spec or code.
A skill your agent uses when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
$ npx skills add farm-fe/farm --skill using-superpowers -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install farm-fe/farm using-superpowers --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/farm-fe/farm.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/using-superpowers .claude/skills/using-superpowers && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "using-superpowers" agent skill from https://github.com/farm-fe/farm/tree/main/.agents/skills/using-superpowers into .claude/skills/using-superpowers/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "using-superpowers", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/farm-fe/farm/tree/main/.agents/skills/using-superpowersType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add farm-fe/farm --skill using-superpowers -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install farm-fe/farm using-superpowers --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/farm-fe/farm.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/using-superpowers .agents/skills/using-superpowers && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "using-superpowers" agent skill from https://github.com/farm-fe/farm/tree/main/.agents/skills/using-superpowers into .agents/skills/using-superpowers/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "using-superpowers", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add farm-fe/farm --skill using-superpowers -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install farm-fe/farm using-superpowers --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/farm-fe/farm.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/using-superpowers .cursor/skills/using-superpowers && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "using-superpowers" agent skill from https://github.com/farm-fe/farm/tree/main/.agents/skills/using-superpowers into .cursor/skills/using-superpowers/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "using-superpowers", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/farm-fe/farm.git --path .agents/skills/using-superpowers--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add farm-fe/farm --skill using-superpowers -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install farm-fe/farm using-superpowers --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/farm-fe/farm.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/using-superpowers .gemini/skills/using-superpowers && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "using-superpowers" agent skill from https://github.com/farm-fe/farm/tree/main/.agents/skills/using-superpowers into .gemini/skills/using-superpowers/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "using-superpowers", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install farm-fe/farm using-superpowersInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add farm-fe/farm --skill using-superpowers -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/farm-fe/farm.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/using-superpowers .github/skills/using-superpowers && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "using-superpowers" agent skill from https://github.com/farm-fe/farm/tree/main/.agents/skills/using-superpowers into .github/skills/using-superpowers/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "using-superpowers", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add farm-fe/farm --skill using-superpowers -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install farm-fe/farm using-superpowers --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/farm-fe/farm.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/using-superpowers .opencode/skills/using-superpowers && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "using-superpowers" agent skill from https://github.com/farm-fe/farm/tree/main/.agents/skills/using-superpowers into .opencode/skills/using-superpowers/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "using-superpowers", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
using-superpowersA skill your agent uses when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
Using Superpowers is an agent skill from farm-fe/farm. Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `references/codex-tools.md`, `references/copilot-tools.md` and `references/gemini-tools.md`).
It sits in Agent Workflows, covering Requirements gathering. The repository describes itself as: Extremely fast Vite-compatible web build tool written in Rust. The licence is MIT.
3 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 2000ef8. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md (its code samples are dot).
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Using Superpowers loads about 1.4k tokens when it runs, and up to ~3.2k if it reads all its reference files. Until then it costs about 44 tokens; SKILL.md has 548 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from farm-fe/farm at commit 2000ef8, republished under its MIT licence (© farm-fe). 548 words, ~1,352 tokens.
.claude/skills/using-superpowers/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.<SUBAGENT-STOP>
If you were dispatched as a subagent to execute a specific task, skip this skill.
</SUBAGENT-STOP>
<EXTREMELY-IMPORTANT>
If you think there is even a 1% chance a skill might apply to what you are doing, you ABSOLUTELY MUST invoke the skill.
IF A SKILL APPLIES TO YOUR TASK, YOU DO NOT HAVE A CHOICE. YOU MUST USE IT.
This is not negotiable. This is not optional. You cannot rationalize your way out of this.
</EXTREMELY-IMPORTANT>
Superpowers skills override default system prompt behavior, but user instructions always take precedence:
If CLAUDE.md, GEMINI.md, or AGENTS.md says "don't use TDD" and a skill says "always use TDD," follow the user's instructions. The user is in control.
In Claude Code: Use the Skill tool. When you invoke a skill, its content is loaded and presented to you—follow it directly. Never use the Read tool on skill files.
In Copilot CLI: Use the skill tool. Skills are auto-discovered from installed plugins. The skill tool works the same as Claude Code's Skill tool.
In Gemini CLI: Skills activate via the activate_skill tool. Gemini loads skill metadata at session start and activates the full content on demand.
In other environments: Check your platform's documentation for how skills are loaded.
Skills use Claude Code tool names. Non-CC platforms: see references/copilot-tools.md (Copilot CLI), references/codex-tools.md (Codex) for tool equivalents. Gemini CLI users get the tool mapping loaded automatically via GEMINI.md.
Invoke relevant or requested skills BEFORE any response or action. Even a 1% chance a skill might apply means that you should invoke the skill to check. If an invoked skill turns out to be wrong for the situation, you don't need to use it.
digraph skill_flow {
"User message received" [shape=doublecircle];
"About to EnterPlanMode?" [shape=doublecircle];
"Already brainstormed?" [shape=diamond];
"Invoke brainstorming skill" [shape=box];
"Might any skill apply?" [shape=diamond];
"Invoke Skill tool" [shape=box];
"Announce: 'Using [skill] to [purpose]'" [shape=box];
"Has checklist?" [shape=diamond];
"Create TodoWrite todo per item" [shape=box];
"Follow skill exactly" [shape=box];
"Respond (including clarifications)" [shape=doublecircle];
"About to EnterPlanMode?" -> "Already brainstormed?";
"Already brainstormed?" -> "Invoke brainstorming skill" [label="no"];
"Already brainstormed?" -> "Might any skill apply?" [label="yes"];
"Invoke brainstorming skill" -> "Might any skill apply?";
"User message received" -> "Might any skill apply?";
"Might any skill apply?" -> "Invoke Skill tool" [label="yes, even 1%"];
"Might any skill apply?" -> "Respond (including clarifications)" [label="definitely not"];
"Invoke Skill tool" -> "Announce: 'Using [skill] to [purpose]'";
"Announce: 'Using [skill] to [purpose]'" -> "Has checklist?";
"Has checklist?" -> "Create TodoWrite todo per item" [label="yes"];
"Has checklist?" -> "Follow skill exactly" [label="no"];
"Create TodoWrite todo per item" -> "Follow skill exactly";
}These thoughts mean STOP—you're rationalizing:
| Thought | Reality |
|---|---|
| "This is just a simple question" | Questions are tasks. Check for skills. |
| "I need more context first" | Skill check comes BEFORE clarifying questions. |
| "Let me explore the codebase first" | Skills tell you HOW to explore. Check first. |
| "I can check git/files quickly" | Files lack conversation context. Check for skills. |
| "Let me gather information first" | Skills tell you HOW to gather information. |
| "This doesn't need a formal skill" | If a skill exists, use it. |
| "I remember this skill" | Skills evolve. Read current version. |
| "This doesn't count as a task" | Action = task. Check for skills. |
| "The skill is overkill" | Simple things become complex. Use it. |
| "I'll just do this one thing first" | Check BEFORE doing anything. |
| "This feels productive" | Undisciplined action wastes time. Skills prevent this. |
| "I know what that means" | Knowing the concept ≠ using the skill. Invoke it. |
When multiple skills could apply, use this order:
"Let's build X" → brainstorming first, then implementation skills. "Fix this bug" → debugging first, then domain-specific skills.
Rigid (TDD, debugging): Follow exactly. Don't adapt away discipline.
Flexible (patterns): Adapt principles to context.
The skill itself tells you which.
Instructions say WHAT, not HOW. "Add X" or "Fix Y" doesn't mean skip workflows.
© farm-fe, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 3 other files (references) in .agents/skills/using-superpowers of farm-fe/farm.
Open the folder on GitHubat commit 2000ef8
We found 56 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 34 other GitHub owners. This page covers the copy in farm-fe/farm, which our catalogue first saw on October 7, 2026.
…and 6 more copies not listed here.
Using Superpowers next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Using Superpowers this skillfarm-fe/farm | 5.6k | 34 repos | ~1.4k | Automated safety check: Pass | MIT | |
| Interview Meaddyosmani/agent-skills | 102k | 6 repos | ~3.8k | Automated safety check: Pass | MIT | |
| Grillingbestofjs/bestofjs | 3.1k | 30 repos | ~464 | Automated safety check: Pass | MIT | |
| Agentic Workflow Designerdotnet/Open-XML-SDK | 4.6k | 2 repos | ~3.5k | Automated safety check: Pass | MIT | |
| Ask User QuestionMemTensor/MemOS | 12k | — | ~1k | Automated safety check: Pass | Apache-2.0 | |
| Brainstorming Before BuildingjnMetaCode/superpowers-zh | 8.3k | — | ~1.8k | Automated safety check: Pass | MIT |
addyosmani/agent-skills
Asks one question at a time, each with a best guess attached, until the agent is about 95 percent sure what you really want, before any plan, spec or code.
bestofjs/bestofjs
Grill the user relentlessly about a plan, decision, or idea.
dotnet/Open-XML-SDK
Interviews you one question at a time about goal, trigger, permissions and data needs, then drafts a single agentic workflow markdown file.
MemTensor/MemOS
Shows a question as a modal in the interface to clarify a task, collect a preference or get approval, since the user cannot see terminal output.
jnMetaCode/superpowers-zh
Turns a rough idea into an approved design before any code is written, sorting the request into spike, bounded or architectural and enforcing an approval gate.
dontbesilent2025/dbskill
Turns a problem you keep running into into a single installable, tested skill, and prepares a GitHub repository only when you ask to share it.
farm-fe/farm
A skill your agent uses when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for…
farm-fe/farm
A skill your agent uses when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and…
farm-fe/farm
Guide for writing idiomatic Rust code based on Apollo GraphQL's best practices handbook.
farm-fe/farm
A skill your agent uses when completing tasks, implementing major features, or before merging to verify work meets requirements
farm-fe/farm
A skill your agent uses when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any…
farm-fe/farm
A universal self-improving agent that learns from ALL skill experiences.
Categories
A skill your agent uses when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions. Using Superpowers is an agent skill from farm-fe/farm.
Using Superpowers fits situations like: starting any conversation - establishes how to find and use skills; requiring Skill tool invocation before ANY response including clarifying questions.
Run `npx skills add farm-fe/farm --skill using-superpowers -a claude-code`. Or copy the skill folder (.agents/skills/using-superpowers in farm-fe/farm) into .claude/skills/using-superpowers in your project. Claude Code loads it when a task matches its description.
Run `npx skills add farm-fe/farm --skill using-superpowers -a codex`. Or copy the skill folder (.agents/skills/using-superpowers in farm-fe/farm) into .agents/skills/using-superpowers in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add farm-fe/farm --skill using-superpowers -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/using-superpowers, .gemini/skills/using-superpowers, .github/skills/using-superpowers and .opencode/skills/using-superpowers in your project.
SKILL.md names no scripts, command-line tools or credentials: Using Superpowers is instructions for the agent only.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Using Superpowers is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 1.4k tokens (SKILL.md is roughly 5.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.8k tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Using Superpowers: Interview Me (addyosmani/agent-skills, 102k stars), Grilling (bestofjs/bestofjs, 3.1k stars), Agentic Workflow Designer (dotnet/Open-XML-SDK, 4.6k stars) and Ask User Question (MemTensor/MemOS, 12k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
farm-fe (a GitHub organization) maintains it in farm-fe/farm, which has 5,594 GitHub stars. The repository holds 20 skills in this directory. The repository was last updated on September 22, 2026.
Source: farm-fe/farm on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.