Process Mapping
FerroxLabs/wayland
Produces a SIPOC process map with suppliers, inputs, process steps, outputs, and customers for a defined business process.
Analyze processes, identify workflows, define boundaries and scope, and map process requirements for specialization creation.
MITAuto-check passed
Install Process Analyzer
$ npx skills add majiayu000/claude-skill-registry --skill process-analyzer -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install majiayu000/claude-skill-registry process-analyzer --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/majiayu000/claude-skill-registry.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/analysis/process-analyzer .claude/skills/process-analyzer && 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 "process-analyzer" agent skill from https://github.com/majiayu000/claude-skill-registry/tree/main/skills/analysis/process-analyzer into .claude/skills/process-analyzer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "process-analyzer", 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/majiayu000/claude-skill-registry/tree/main/skills/analysis/process-analyzerType 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 majiayu000/claude-skill-registry --skill process-analyzer -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install majiayu000/claude-skill-registry process-analyzer --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/majiayu000/claude-skill-registry.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/analysis/process-analyzer .agents/skills/process-analyzer && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "process-analyzer" agent skill from https://github.com/majiayu000/claude-skill-registry/tree/main/skills/analysis/process-analyzer into .agents/skills/process-analyzer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "process-analyzer", 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 majiayu000/claude-skill-registry --skill process-analyzer -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install majiayu000/claude-skill-registry process-analyzer --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/majiayu000/claude-skill-registry.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/analysis/process-analyzer .cursor/skills/process-analyzer && 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 "process-analyzer" agent skill from https://github.com/majiayu000/claude-skill-registry/tree/main/skills/analysis/process-analyzer into .cursor/skills/process-analyzer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "process-analyzer", 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/majiayu000/claude-skill-registry.git --path skills/analysis/process-analyzer--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 majiayu000/claude-skill-registry --skill process-analyzer -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install majiayu000/claude-skill-registry process-analyzer --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/majiayu000/claude-skill-registry.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/analysis/process-analyzer .gemini/skills/process-analyzer && 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 "process-analyzer" agent skill from https://github.com/majiayu000/claude-skill-registry/tree/main/skills/analysis/process-analyzer into .gemini/skills/process-analyzer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "process-analyzer", 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 majiayu000/claude-skill-registry process-analyzerInstalls 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 majiayu000/claude-skill-registry --skill process-analyzer -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/majiayu000/claude-skill-registry.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/analysis/process-analyzer .github/skills/process-analyzer && 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 "process-analyzer" agent skill from https://github.com/majiayu000/claude-skill-registry/tree/main/skills/analysis/process-analyzer into .github/skills/process-analyzer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "process-analyzer", 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 majiayu000/claude-skill-registry --skill process-analyzer -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install majiayu000/claude-skill-registry process-analyzer --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/majiayu000/claude-skill-registry.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/analysis/process-analyzer .opencode/skills/process-analyzer && 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 "process-analyzer" agent skill from https://github.com/majiayu000/claude-skill-registry/tree/main/skills/analysis/process-analyzer into .opencode/skills/process-analyzer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "process-analyzer", 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
process-analyzer- GitHub stars
- 666
- Used in
- 1 other repo
- Token cost
- ~661 tokens
- SKILL.md length
- 174 words
- Files
- 2
- Skills in repo
- 971
- Repo updated
- First seen
- Licence
- MIT
At a glance
Analyze processes, identify workflows, define boundaries and scope, and map process requirements for specialization creation.
- Works in 4 steps: Workflow Analysis → Process Boundary Definition → Dependency Mapping → …
- SKILL.md covers Overview, Capabilities, Output Format and Process Integration, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Process Analyzer is an agent skill from majiayu000/claude-skill-registry. Analyze processes, identify workflows, define boundaries and scope, and map process requirements for specialization creation.
Its SKILL.md is about 660 tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `metadata.json`).
The repository describes itself as: Searchable Claude Code skills catalog with source-linked guides and generated registry artifacts. The licence is MIT.
Example prompts
- “/process-analyzer”
Requirements
- Pre-approved tools (allowed-tools): Read, Glob, Grep
Workflow steps
4 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 000116a. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
ReadGlobGrep
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are json).
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
Process Analyzer loads about 661 tokens when it runs. Until then it costs about 36 tokens; SKILL.md has 174 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
The full file from majiayu000/claude-skill-registry at commit 000116a, republished under its MIT licence (© majiayu000). 174 words, ~661 tokens.
Download SKILL.mdSave it as
.claude/skills/process-analyzer/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- process-analyzer
- description
- Analyze processes, identify workflows, define boundaries and scope, and map process requirements for specialization creation.
- allowed-tools
- Read, Glob, Grep
- metadata.author
- babysitter-sdk
- metadata.version
- 1.0.0
- metadata.category
- analysis
- metadata.backlog-id
- SK-META-002
process-analyzer
You are process-analyzer - a specialized skill for analyzing process requirements and workflows within the Babysitter SDK framework.
Overview
This skill analyzes processes including:
- Workflow identification
- Process boundary definition
- Input/output mapping
- Dependency analysis
- Quality criteria identification
Capabilities
1. Workflow Analysis
Identify workflows and patterns:
- Read domain documentation
- Extract process patterns
- Map workflow steps
- Identify decision points
2. Process Boundary Definition
Define clear process boundaries:
- Determine start conditions
- Define end conditions
- Identify inputs required
- Specify outputs produced
3. Dependency Mapping
Map process dependencies:
- Identify prerequisite processes
- Map skill dependencies
- Identify agent requirements
- Document external dependencies
4. Quality Criteria Definition
Define quality criteria:
- Identify success metrics
- Define quality gates
- Specify validation points
- Document acceptance criteria
Output Format
{
"processName": "process-name",
"description": "Process description",
"category": "core|support|quality",
"priority": "high|medium|low",
"workflow": {
"steps": ["step1", "step2", "step3"],
"decisionPoints": ["decision1"],
"loops": ["refinement-loop"]
},
"boundaries": {
"startConditions": ["condition1"],
"endConditions": ["condition1"],
"inputs": { "param1": "type" },
"outputs": { "result": "type" }
},
"dependencies": {
"processes": ["process1"],
"skills": ["skill1"],
"agents": ["agent1"]
},
"qualityCriteria": {
"metrics": ["metric1"],
"gates": ["gate1"],
"validations": ["validation1"]
}
}Process Integration
This skill integrates with:
phase2-identify-processes.js- Process identificationprocess-creation.js- Requirements analysisspecialization-creation.js- Phase 2
Best Practices
- Comprehensive Analysis: Consider all aspects
- Clear Boundaries: Define precise scope
- Traceable Dependencies: Document all dependencies
- Measurable Quality: Use quantifiable metrics
- Categorized Output: Organize by type
Constraints
- Read-only analysis
- Focus on process structure
- Document assumptions
- Prioritize by impact
© majiayu000, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file in skills/analysis/process-analyzer of majiayu000/claude-skill-registry.
- SKILL.md
- metadata.json
Open the folder on GitHubat commit 000116a
Used in 1 other repository
We found 2 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in majiayu000/claude-skill-registry, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Process Analyzer 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 |
|---|---|---|---|---|---|---|
| Process Analyzer this skillmajiayu000/claude-skill-registry | 666 | 1 repos | ~661 | Automated safety check: Pass | MIT | |
| Process MappingFerroxLabs/wayland | 608 | — | ~3.4k | Automated safety check: Pass | Apache-2.0 | |
| Process Mappingrevfactory/harness-100 | 1.3k | — | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| Detecting Process Hollowing Techniquemukul975/Anthropic-Cybersecurity-Skills | 34k | — | ~1.2k | Automated safety check: Pass | Apache-2.0 | |
| Process Mappingrevfactory/harness-100 | 1.3k | — | ~736 | Automated safety check: Pass | Apache-2.0 | |
| Token Mapnexu-io/open-design | 100k | — | ~1.4k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Process Mapping
revfactory/harness-100
process mapping method. An agent skill from revfactory/harness-100.
Detecting Process Hollowing Technique
mukul975/Anthropic-Cybersecurity-Skills
Detect process hollowing (MITRE T1055.012) by analyzing memory-mapped sections, hollowed process indicators, and parent-child anomalies using EDR telemetry, Volatility's malfind plugin, pe-sieve…
Process Mapping
revfactory/harness-100
프로세스 매핑 방법론. An agent skill from revfactory/harness-100.
Token Map
nexu-io/open-design
Map an extracted Figma / source-code token bag onto the active OD design system, producing a deterministic mapping the generate stage can consume.
Maps Geography
asgeirtj/system_prompts_leaks
Accurate maps from real geo data — use for any map, or whenever geography would make a good graphic for a deliverable
More from majiayu000/claude-skill-registry
All 971 skills in this repoDeep Research
majiayu000/claude-skill-registry
Multi-source deep research using firecrawl and exa MCPs. An agent skill from majiayu000/claude-skill-registry.
Exa Search
majiayu000/claude-skill-registry
Neural search via Exa MCP for web, code, and company research.
Fal AI Media
majiayu000/claude-skill-registry
Unified media generation via fal.ai MCP — image, video, and audio.
Bgpt Paper Search
majiayu000/claude-skill-registry
Search scientific papers and retrieve structured experimental data extracted from full-text studies via the BGPT MCP server.
Bio Alignment Pairwise
majiayu000/claude-skill-registry
Perform pairwise sequence alignment using Biopython Bio.Align.PairwiseAligner.
Open Notebook
majiayu000/claude-skill-registry
Self-hosted, open-source alternative to Google NotebookLM for AI-powered research and document analysis.
Questions about Process Analyzer
What does Process Analyzer do?
Analyze processes, identify workflows, define boundaries and scope, and map process requirements for specialization creation. Process Analyzer is an agent skill from majiayu000/claude-skill-registry. Analyze processes, identify workflows, define boundaries and scope, and map process requirements for specialization creation.
How do I install Process Analyzer in Claude Code?
Run `npx skills add majiayu000/claude-skill-registry --skill process-analyzer -a claude-code`. Or copy the skill folder (skills/analysis/process-analyzer in majiayu000/claude-skill-registry) into .claude/skills/process-analyzer in your project. Claude Code loads it when a task matches its description.
How do I install Process Analyzer in Codex?
Run `npx skills add majiayu000/claude-skill-registry --skill process-analyzer -a codex`. Or copy the skill folder (skills/analysis/process-analyzer in majiayu000/claude-skill-registry) into .agents/skills/process-analyzer in your project. Codex loads it when a task matches its description.
Can I use Process Analyzer 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 majiayu000/claude-skill-registry --skill process-analyzer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/process-analyzer, .gemini/skills/process-analyzer, .github/skills/process-analyzer and .opencode/skills/process-analyzer in your project.
What does Process Analyzer need to run?
SKILL.md names no scripts, command-line tools or credentials: Process Analyzer is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Glob, Grep.
Does Process Analyzer 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 Process Analyzer 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 Process Analyzer use?
Process Analyzer is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Process Analyzer use?
About 661 tokens (SKILL.md is roughly 2.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Process Analyzer?
Skills that share tags, products or a category with Process Analyzer: Process Mapping (FerroxLabs/wayland, 608 stars), Process Mapping (revfactory/harness-100, 1.3k stars), Detecting Process Hollowing Technique (mukul975/Anthropic-Cybersecurity-Skills, 34k stars) and Process Mapping (revfactory/harness-100, 1.3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Process Analyzer?
majiayu000 (a GitHub user) maintains it in majiayu000/claude-skill-registry, which has 666 GitHub stars. The repository holds 971 skills in this directory. The repository was last updated on October 7, 2026.
Source: majiayu000/claude-skill-registry on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.