Tutti Architecture Review
tutti-os/tutti
Review tutti git diffs for project structure, layering, module ownership, and duplicate event-center infrastructure by planning focused architecture review tasks, then having the main agent…
Answers how-does-this-work and where-should-this-live questions by exploring the codebase with read-only subagents and writing an onboarding-depth explanation.
Install How Does This Work Explainer
$ npx skills add cursor/plugins --skill how -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install cursor/plugins how --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/cursor/plugins.git skills-src && mkdir -p .claude/skills && cp -r skills-src/pstack/skills/how .claude/skills/how && 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 "how" agent skill from https://github.com/cursor/plugins/tree/main/pstack/skills/how into .claude/skills/how/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "how", 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/cursor/plugins/tree/main/pstack/skills/howType 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 cursor/plugins --skill how -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install cursor/plugins how --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cursor/plugins.git skills-src && mkdir -p .agents/skills && cp -r skills-src/pstack/skills/how .agents/skills/how && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "how" agent skill from https://github.com/cursor/plugins/tree/main/pstack/skills/how into .agents/skills/how/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "how", 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 cursor/plugins --skill how -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install cursor/plugins how --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cursor/plugins.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/pstack/skills/how .cursor/skills/how && 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 "how" agent skill from https://github.com/cursor/plugins/tree/main/pstack/skills/how into .cursor/skills/how/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "how", 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/cursor/plugins.git --path pstack/skills/how--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 cursor/plugins --skill how -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install cursor/plugins how --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cursor/plugins.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/pstack/skills/how .gemini/skills/how && 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 "how" agent skill from https://github.com/cursor/plugins/tree/main/pstack/skills/how into .gemini/skills/how/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "how", 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 cursor/plugins howInstalls 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 cursor/plugins --skill how -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/cursor/plugins.git skills-src && mkdir -p .github/skills && cp -r skills-src/pstack/skills/how .github/skills/how && 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 "how" agent skill from https://github.com/cursor/plugins/tree/main/pstack/skills/how into .github/skills/how/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "how", 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 cursor/plugins --skill how -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install cursor/plugins how --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cursor/plugins.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/pstack/skills/how .opencode/skills/how && 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 "how" agent skill from https://github.com/cursor/plugins/tree/main/pstack/skills/how into .opencode/skills/how/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "how", 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.
Facts
- Skill name
how- GitHub stars
- 10k
- Used in
- 6 other repos
- Token cost
- ~771 tokens
- SKILL.md length
- 395 words
- Files
- 3 (incl. references)
- Skills in repo
- 99
- Repo updated
- First seen
- Licence
- None found
At a glance
Answers how-does-this-work and where-should-this-live questions by exploring the codebase with read-only subagents and writing an onboarding-depth explanation.
- Works in 3 steps: Assess Complexity → Synthesize (complex questions only) → Present
- Understanding how a subsystem works before changing it
- SKILL.md covers Step 1. Assess Complexity, Step 2a. Explore (complex…, Step 2b. Direct Explain… and Step 3. Synthesize (complex…, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
This skill answers questions such as how a subsystem works, where a piece of code should live or which package owns something. It explores the codebase and writes an architectural explanation pitched at a senior engineer joining that area: enough to form a working mental model without reading like annotated source. If the scope is unclear, the agent states its interpretation, explores anyway and lets you redirect.
It first judges complexity. A narrow question about one module or function goes to a single read-only subagent that explores and explains in one pass. A subsystem spanning several files or services, a cross-cutting feature or a full overview is split into two to four exploration angles run in parallel by read-only explorers, whose findings a second subagent then synthesizes into one explanation. Prompts come from `references/explorer-prompt.md` and `references/explainer-prompt.md`, and model choices come from a `pstack-models.mdc` rule with built-in defaults. For the motivation behind a design, a separate why skill is the better fit.
When your agent uses it
- Understanding how a subsystem works before changing it
- Deciding which package or layer should own a new piece of code
- Building a mental model of an unfamiliar part of a codebase
Example prompts
- “How does the job scheduler decide which task runs next?”
- “Walk me through the request flow in the auth service before I change it.”
- “Which package should own the retry logic, and is the API layer the right place for it?”
Requirements
- A subagent or Task tool that can run read-only subagents
Workflow steps
3 steps, taken from the step headings in SKILL.md.
- Assess Complexity
- Synthesize (complex questions only)
- Present
What it can do on your machine
Read from SKILL.md and the folder at commit 9f451cf. It shows what the files ask for, not the result of running them.
Tool permissions
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.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
How Does This Work Explainer loads about 771 tokens when it runs, and up to ~2.2k if it reads all its reference files. Until then it costs about 75 tokens; SKILL.md has 395 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.
Safety
Auto-check passed
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.
SKILL.md
Without a licence we can't republish the file, so here is its outline and opening line. It has 395 words (~771 tokens).
“Explore the codebase to answer "how does X work?" questions. Produce architectural explanations at the level of a senior engineer onboarding onto a subsystem, enough to build a working mental model, not so much that it reads like annotated source…”
- name
- how
- disable-model-invocation
- true
Files
SKILL.md and 2 other files (references) in pstack/skills/how of cursor/plugins.
- SKILL.md
- references/explainer-prompt.md
- references/explorer-prompt.md
Open the folder on GitHubat commit 9f451cf
Used in 6 other repositories
We found 6 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 6 other GitHub owners. This page covers the copy in cursor/plugins, which our catalogue first saw on October 7, 2026.
Compare with similar skills
How Does This Work Explainer 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 |
|---|---|---|---|---|---|---|
| How Does This Work Explainer this skillcursor/plugins | 10k | 6 repos | ~771 | Automated safety check: Pass | None | |
| Tutti Architecture Reviewtutti-os/tutti | 3.8k | — | ~2.3k | Automated safety check: Pass | Apache-2.0 | |
| Codebase Research QuestionsWirasm/prp | 2.3k | — | ~2.8k | Automated safety check: Pass | MIT | |
| aspens Project Conventionsaspenkit/aspens | 102 | — | ~1.6k | Automated safety check: Pass | MIT | |
| Exploreyonatangross/orchestkit | 288 | — | ~3.9k | Automated safety check: Notes | MIT | |
| Deepwiki Rssopaco/deepwiki-rs | 3.1k | — | ~748 | Automated safety check: Pass | MIT |
Similar skills
Codebase Research Questions
Wirasm/prp
Answers where and how questions about a codebase with parallel research agents and a write-up where every claim cites a file and line, describing only what exists.
aspens Project Conventions
aspenkit/aspens
Orientation to the aspens codebase for agents working on the CLI itself: its Node.js stack, commands, module layout and debug settings.
Explore
yonatangross/orchestkit
Multi-angle codebase exploration spawning 3-5 parallel agents for code structure, data flow, architecture patterns, and health assessment.
Deepwiki Rs
sopaco/deepwiki-rs
AI-powered Rust documentation generation engine for comprehensive codebase analysis, C4 architecture diagrams, and automated technical documentation.
GitDiagram Repository Overview
ahmedkhaleel2004/gitdiagram
Explains the architecture of a public GitHub repository through GitDiagram: how the code is organized, the main components with paths, and a Mermaid diagram.
More from cursor/plugins
All 99 skills in this repo- Official
Show Me Your Work Decision Log
cursor/plugins
Keeps a TSV decision log for long or unattended agent runs, one row per decision with what, why, evidence and result, so a reviewer can check the work later.
- Official
Code Design Rationale Investigator
cursor/plugins
Digs into why code is shaped the way it is by checking git history, pull requests and connected tools in parallel, then reporting a cited read on the tradeoffs.
- Official
Reflect on Session Learnings
cursor/plugins
Starts three parallel reviewer subagents over the current conversation transcript, then turns their findings into concrete edits to existing skills.
- Official
Technical Writing Standard
cursor/plugins
Applies four layers of technical-writing rules to docs, RFCs, readmes, PR descriptions and commit messages so a tired engineer follows them on the first read.
- Official
Advisor Mode
cursor/plugins
Adds a second, stronger model that the main agent consults before major decisions, when stuck and before finishing, controlled by /advisor commands.
- Official
Make PR Easy To Review
cursor/plugins
Prepare PRs for review by cleaning noisy history, improving PR descriptions, and adding reviewer guidance without changing code behavior.
Related
Categories
Questions about How Does This Work Explainer
What does How Does This Work Explainer do?
Answers how-does-this-work and where-should-this-live questions by exploring the codebase with read-only subagents and writing an onboarding-depth explanation. This skill answers questions such as how a subsystem works, where a piece of code should live or which package owns something. It explores the codebase and writes an architectural explanation pitched at a senior engineer joining that area: enough to form a working mental model without reading like annotated source.
When should I use How Does This Work Explainer?
How Does This Work Explainer fits situations like: understanding how a subsystem works before changing it; deciding which package or layer should own a new piece of code; building a mental model of an unfamiliar part of a codebase.
How do I install How Does This Work Explainer in Claude Code?
Run `npx skills add cursor/plugins --skill how -a claude-code`. Or copy the skill folder (pstack/skills/how in cursor/plugins) into .claude/skills/how in your project. Claude Code loads it when a task matches its description.
How do I install How Does This Work Explainer in Codex?
Run `npx skills add cursor/plugins --skill how -a codex`. Or copy the skill folder (pstack/skills/how in cursor/plugins) into .agents/skills/how in your project. Codex loads it when a task matches its description.
Can I use How Does This Work Explainer in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add cursor/plugins --skill how -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/how, .gemini/skills/how, .github/skills/how and .opencode/skills/how in your project.
What does How Does This Work Explainer need to run?
SKILL.md names no scripts, command-line tools or credentials: How Does This Work Explainer is instructions for the agent only. Our summary lists: A subagent or Task tool that can run read-only subagents.
Does How Does This Work Explainer access the network?
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.
Is How Does This Work Explainer safe to install?
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.
What licence does How Does This Work Explainer use?
No licence was found for How Does This Work Explainer or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.
How many tokens does How Does This Work Explainer use?
About 771 tokens (SKILL.md is roughly 3.1k 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.4k tokens, read only when the agent opens those files.
What are the alternatives to How Does This Work Explainer?
Skills that share tags, products or a category with How Does This Work Explainer: Tutti Architecture Review (tutti-os/tutti, 3.8k stars), Codebase Research Questions (Wirasm/prp, 2.3k stars), aspens Project Conventions (aspenkit/aspens, 102 stars) and Explore (yonatangross/orchestkit, 288 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains How Does This Work Explainer?
cursor (a GitHub organization, an official publisher) maintains it in cursor/plugins, which has 10,130 GitHub stars. The repository holds 99 skills in this directory. The repository was last updated on October 6, 2026.
Source: cursor/plugins on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.