⏳ This skill is pending AI review.
Scores will appear once the review pipeline completes.
how-it-works
Create or refresh a visual, evidence-aware HOW_IT_WORKS.md for a non-technical product owner. Use when someone asks how a codebase, product flow, agent loop, data flow, module, or user request works, or when product-visible behavior changed and the living explanation must be updated.
Choose how to use this skill
You do not need every option. Choose the path your AI client supports. The stable page stays the same; versioned files are immutable.
1. Native installer
This listing has no registered native installer command. Use the complete package or source fallback below, depending on what your client supports.
Do not guess an installer command or replace an existing version without reviewing the diff.
2. Complete package recommended
Download the ZIP when available. It includes SKILL.md plus the references, security notes and version metadata.
No complete ProSkills package is published for this listing yet.3. Prompt-only
Copy the prompt above when the agent can read the stable page or when you want to adopt the workflow without installing a skill.
Need only the instruction file?
Download SKILL.md only if your client requires a single file. The complete ZIP is safer for a full installation because it preserves the references and release context.
No path installs or executes anything by itself. Your agent still needs access to the project files. Before updating, compare the installed version and review the diff.
// RATINGS
Not yet listed on ClawHub or SkillsMP
// README
How It Works
The code keeps changing. The product truth gets blurrier.
When implementation is a black box, every iteration makes the current system harder to explain. This skill turns the current repository into a living, visual product explanation. Give a product owner one place to see what the product does, how a request travels, and what the evidence proves.

| Understand current behavior | Separate proof from assumption | Know where to investigate |
|---|---|---|
| Follow a user request from input to result. | Distinguish code, local tests, real runtime, and user acceptance. | Use symptoms to find the responsible module and next check. |

Five-minute first use
Use an Agent Skills client with repository access and Python 3.9 or later.
The npx route also requires Node.js and npm.
Without npx, use manual installation.
Install the main skill:
npx skills add joevilcai666/how-it-works-skill --skill how-it-works
Open your project in the client. Send this prompt:
$how-it-works
Create HOW_IT_WORKS.md for a non-technical product owner in English.
Trace one important user request. Use 2–4 useful Mermaid diagrams.
Separate code, local tests, real runtime, and user acceptance evidence.
Mark missing evidence. Use synthetic examples and omit private records.
The first run adds project-local maintenance rules to AGENTS.md.
It preserves unrelated instructions and adds a root AGENTS.md import to existing Claude project instructions when needed.
Root CLAUDE.md uses @AGENTS.md. .claude/CLAUDE.md uses @../AGENTS.md.
If both files exist, setup checks and updates both. It does not create either file or change global instructions.
If Markdown context is ambiguous or unsupported, setup stops before any instruction-file edit. Simplify the markup before another run.
The agent then creates or refreshes one HOW_IT_WORKS.md in your language.
Large repositories can take more than five minutes to inspect.
See the synthetic Acorn Tasks project and its example product explanation. All demo data is fictional. The example does not prove production operation.
Release status: v0.1.1 is public.
v0.1.1 verification confirms isolated public installs for Codex, Claude Code, and npx skills.
The exact ZIP and its checksum appear in that record.
Official directories have no submission or acceptance yet. See the distribution register.
The skills.sh page is discoverable as of 2026-10-15.
The page does not expose v0.1.1 identity or the ZIP checksum. Visibility does not prove completed audits, install counts, or ranking.
Install options
Codex: skill or portable plugin
Use the npx skills command above for the main skill.
For the portable plugin, add this repository as a marketplace and install its plugin:
codex plugin marketplace add joevilcai666/how-it-works-skill
codex plugin add how-it-works@how-it-works-skill
For a local checkout, add its directory instead:
git clone https://github.com/joevilcai666/how-it-works-skill.git
codex plugin marketplace add ./how-it-works-skill
codex plugin add how-it-works@how-it-works-skill
Keep the full checkout for this route. The root plugin.json describes the portable package.
The Codex overlay and repository marketplace point to the same skills/ directory.
The plugin also includes a small setup skill.
Codex CLI 0.162.1 installed this public plugin in an isolated configuration.
Use --ref v0.1.1 on the marketplace command to select the verified release.
Claude Code: repository marketplace
Run these commands in Claude Code:
/plugin marketplace add joevilcai666/how-it-works-skill
/plugin install how-it-works@how-it-works-skill
Use the loaded skill through the client's skill menu or supported invocation syntax. The package includes a Claude manifest and a repository marketplace. Claude Code 2.1.218 installed version 0.1.1 through this public marketplace. The document trial still requires valid model authentication. Installation does not prove document acceptance.
Generic Agent Skills clients: manual copy
Download the repository or clone it. Copy the complete main skill directory:
git clone https://github.com/joevilcai666/how-it-works-skill.git
cp -R how-it-works-skill/skills/how-it-works <client-skill-directory>/how-it-works
Replace <client-skill-directory> with your client's documented skill directory.
Keep SKILL.md, references/, assets/, and scripts/ together.
Invoke how-it-works through your client's supported syntax.
Generic clients do not need the plugin manifests or setup adapter.
Compatibility and evidence
| Client or component | Available package support | Verified here | Still unverified |
|---|---|---|---|
| Codex | Agent Skills, portable plugin.json, Codex overlay, setup skill | Public v0.1.1 plugin install and both skill directories. Earlier v0.1.0 synthetic document | Model use through the public plugin and full acceptance |
| Claude Code | Shared skills, plugin manifest, repository marketplace | Public v0.1.1 install, enabled plugin, strict validation. Earlier local skill discovery | New document run and model use of project imports. Earlier trial returned HTTP 401 |
| Generic Agent Skills client | Complete skills/how-it-works/ directory | Public npx install and copied-file equality | Each independent client's document execution |
| Instruction updater | Python 3.9+, English and Chinese maintenance blocks | Idempotency, preservation, refusal cases, local unit tests | Every filesystem and instruction configuration |
The recorded synthetic agent run met 6 of 7 rubric checks. It used two diagrams. The case requires three, while the skill permits two to four. This result does not prove cross-client compatibility or user acceptance.
Document language follows the request. Setup blocks support English and Simplified Chinese. Other languages use the English setup block while the document keeps the requested language.
What the skill changes
The agent reads project instructions, product sources, code, tests, and available runtime evidence. It traces a representative request and writes current behavior, diagrams, module responsibilities, concepts, diagnosis guidance, and limitations. Later runs update the affected content and remove false statements. The maintenance block asks future agents to keep the document current after product changes. It is an instruction contract, not a background watcher or an automatic enforcement hook.
See how this package works, the main workflow, and the evidence rules.
Privacy
The skill adds no telemetry and no repository upload service. Its updater operates on local project instruction files. Your AI client still controls model access, permissions, and its own data policy. Third-party installers can have their own telemetry. Review their policy or use the manual copy route.
Keep secrets, private messages, and sensitive records out of generated examples and public reports. Use synthetic fixtures and redacted evidence. A privacy scan cannot prove that every possible disclosure is absent. Report vulnerabilities through private reporting.
Contribute
Send a synthetic bug example, a client compatibility report, or a clear improvement request. Read [CONTRIBUTING.md](C
// HOW IT'S BUILT
KEY FILES