Debugging Executions
n8n-io/n8n
Debug failed or wrong-output workflow executions using executions tools.
This skill should be used when the user asks to "apply a pattern", "use a blueprint", "implement [pattern] from [source]", "what blueprints do I have", "list patterns", "adapt this pattern", or…
$ npx skills add adamthewilliam/grepika --skill apply-pattern -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install adamthewilliam/grepika apply-pattern --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/adamthewilliam/grepika.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/grepika/skills/apply-pattern .claude/skills/apply-pattern && 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 "apply-pattern" agent skill from https://github.com/adamthewilliam/grepika/tree/main/plugins/grepika/skills/apply-pattern into .claude/skills/apply-pattern/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "apply-pattern", 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/adamthewilliam/grepika/tree/main/plugins/grepika/skills/apply-patternType 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 adamthewilliam/grepika --skill apply-pattern -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install adamthewilliam/grepika apply-pattern --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/adamthewilliam/grepika.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/grepika/skills/apply-pattern .agents/skills/apply-pattern && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "apply-pattern" agent skill from https://github.com/adamthewilliam/grepika/tree/main/plugins/grepika/skills/apply-pattern into .agents/skills/apply-pattern/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "apply-pattern", 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 adamthewilliam/grepika --skill apply-pattern -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install adamthewilliam/grepika apply-pattern --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/adamthewilliam/grepika.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/grepika/skills/apply-pattern .cursor/skills/apply-pattern && 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 "apply-pattern" agent skill from https://github.com/adamthewilliam/grepika/tree/main/plugins/grepika/skills/apply-pattern into .cursor/skills/apply-pattern/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "apply-pattern", 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/adamthewilliam/grepika.git --path plugins/grepika/skills/apply-pattern--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 adamthewilliam/grepika --skill apply-pattern -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install adamthewilliam/grepika apply-pattern --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/adamthewilliam/grepika.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/grepika/skills/apply-pattern .gemini/skills/apply-pattern && 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 "apply-pattern" agent skill from https://github.com/adamthewilliam/grepika/tree/main/plugins/grepika/skills/apply-pattern into .gemini/skills/apply-pattern/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "apply-pattern", 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 adamthewilliam/grepika apply-patternInstalls 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 adamthewilliam/grepika --skill apply-pattern -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/adamthewilliam/grepika.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/grepika/skills/apply-pattern .github/skills/apply-pattern && 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 "apply-pattern" agent skill from https://github.com/adamthewilliam/grepika/tree/main/plugins/grepika/skills/apply-pattern into .github/skills/apply-pattern/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "apply-pattern", 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 adamthewilliam/grepika --skill apply-pattern -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install adamthewilliam/grepika apply-pattern --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/adamthewilliam/grepika.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/grepika/skills/apply-pattern .opencode/skills/apply-pattern && 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 "apply-pattern" agent skill from https://github.com/adamthewilliam/grepika/tree/main/plugins/grepika/skills/apply-pattern into .opencode/skills/apply-pattern/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "apply-pattern", 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.
apply-patternThis skill should be used when the user asks to "apply a pattern", "use a blueprint", "implement [pattern] from [source]", "what blueprints do I have", "list patterns", "adapt this pattern", or…
Apply Pattern is an agent skill from adamthewilliam/grepika. This skill should be used when the user asks to "apply a pattern", "use a blueprint", "implement [pattern] from [source]", "what blueprints do I have", "list patterns", "adapt this pattern", or mentions keywords related to applying previously extracted architectural patterns to their current project.
Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts. Compatibility notes: Requires grepika MCP server.
It sits in Development. It works with Model Context Protocol. The licence is MIT.
4 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit f035a18. It shows what the files ask for, not the result of running them.
Pre-approves these tools, so the agent can use them without asking each time:
mcp__grepika__searchmcp__grepika__refsmcp__grepika__outlinemcp__grepika__tocmcp__grepika__getmcp__grepika__structural_searchmcp__grepika__add_workspaceBashReadFrom allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).
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.
Requires grepika MCP server.
From compatibility in the SKILL.md frontmatter.
Apply Pattern loads about 1.4k tokens when it runs. Until then it costs about 79 tokens; SKILL.md has 398 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 noted patterns worth knowing about, such as sudo or a known installer.
allowed-tools: mcp__grepika__search, mcp__grepika__refs, mcp__grepika__outline, mcp__grepika__toc, mcp__grepika__geAutomated 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 adamthewilliam/grepika at commit f035a18, republished under its MIT licence (© adamthewilliam). 398 words, ~1,416 tokens.
.claude/skills/apply-pattern/SKILL.md (or your agent's skills folder).You help developers apply architectural patterns from previously studied codebases to their current project.
Arguments: $ARGUMENTS
Determine the action from the arguments:
--list → List all available blueprints<source> (single word, no colon) → List patterns in that blueprint<source>:<pattern> → Apply a specific pattern to the current project<pattern> (contains hyphen, no colon) → Search all blueprints for this pattern nameIf no arguments provided, run --list.
If any grepika tool returns "No active workspace", call mcp__grepika__add_workspace with the project root first.
--list)Use Bash to list available blueprints:
ls -1 ~/.claude/blueprints/ 2>/dev/null || echo "No blueprints found. Use /study to extract patterns from a codebase first."For each blueprint found, use Bash to extract the frontmatter:
head -10 ~/.claude/blueprints/*/blueprint.mdOutput:
## Available Blueprints
| Source | Patterns | Studied | Focus |
|--------|----------|---------|-------|
| [name] | [count] | [date] | [focus] |
Use `/apply-pattern <source>` to see patterns, or `/apply-pattern <source>:<pattern>` to apply one.<source>)Use Read to read ~/.claude/blueprints/<source>/blueprint.md.
Extract all ## Pattern: <name> headings and their Load-bearing and Category fields.
Output:
## Patterns in [source]
| # | Pattern | Load-bearing | Category |
|---|---------|-------------|----------|
| 1 | [name] | yes/no | [category] |
### Build Order
[from the blueprint's Build Order section]
Use `/apply-pattern [source]:[pattern-name]` to apply a pattern.<source>:<pattern>)This is the core workflow.
Use Read to read ~/.claude/blueprints/<source>/blueprint.md.
Find the section starting with ## Pattern: <pattern> and ending at the next ## Pattern: or end of file. Extract:
If the pattern is not found, list available patterns and suggest the closest match.
Use grepika tools to analyze the target project:
mcp__grepika__toc — directory structure and languagemcp__grepika__search with mode: "fts" — find existing code related to the pattern's domainmcp__grepika__outline — structure of files where the pattern would be appliedmcp__grepika__refs — existing symbols that the pattern would interact withCompare the source pattern with the target project's:
spawn_blocking → Node.js worker_threads)Output:
## Applying Pattern: [pattern-name]
> From blueprint: [source]
### Pattern Summary
[What/Why from the blueprint — brief]
### Your Project Context
- **Language**: [target language/framework]
- **Relevant existing code**: [files/symbols that relate to this pattern]
- **What you already have**: [any partial implementation that exists]
- **What's missing**: [what needs to be built]
### Adaptation Plan
#### Step 1: [first thing to implement]
**Where**: `path/to/file.ext`
**What**: [specific guidance]
**Source reference**: [what the source codebase does at this point]
#### Step 2: [next thing]
...
### Key Differences from Source
| Aspect | Source ([source]) | Your Project |
|--------|-------------------|--------------|
| [aspect] | [source approach] | [recommended approach] |
### Dependencies to Add
| Package | Purpose | Alternative |
|---------|---------|-------------|
| [name] | [why needed] | [alternative if any] |
### What to Watch For
- [pitfall or edge case from the source pattern]
- [adaptation concern specific to the target project]<pattern>)Use Bash to search across all blueprints:
grep -rl "## Pattern: .*<pattern>" ~/.claude/blueprints/*/blueprint.md 2>/dev/nullList matches and which blueprint they come from.
© adamthewilliam, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in plugins/grepika/skills/apply-pattern of adamthewilliam/grepika.
Open the folder on GitHubat commit f035a18
Apply Pattern 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 |
|---|---|---|---|---|---|---|
| Apply Pattern this skilladamthewilliam/grepika | 138 | — | ~1.4k | Automated safety check: Notes | MIT | |
| Debugging Executionsn8n-io/n8n | 207k | — | ~2.6k | Automated safety check: Pass | Custom licence | |
| Analyze Logsactivepieces/activepieces | 25k | 1 repos | ~1.6k | Automated safety check: Pass | MIT | |
| ReleasePrefectHQ/fastmcp | 28k | — | ~2.9k | Automated safety check: Pass | Apache-2.0 | |
| Claude Code Skillcodeaashu/claude-code | 3.4k | 1 repos | ~2.7k | Automated safety check: Pass | Proprietary | |
| Run Nx Generatornrwl/nx | 29k | 2 repos | ~592 | Automated safety check: Notes | MIT |
n8n-io/n8n
Debug failed or wrong-output workflow executions using executions tools.
activepieces/activepieces
Analyze application logs from the .evlog/logs/ directory. An agent skill from activepieces/activepieces.
PrefectHQ/fastmcp
Cut a FastMCP release end to end. An agent skill from PrefectHQ/fastmcp.
codeaashu/claude-code
Development conventions and architecture guide for the Claude Code CLI repository.
nrwl/nx
Run Nx generators with prioritization for workspace-plugin generators.
langbot-app/LangBot
Guides building, debugging and testing LangBot plugins: components, SDK calls, README and locale rules, SDK pitfalls and WebSocket-based testing.
adamthewilliam/grepika
This skill should be used when the user asks to "analyze impact of changes", "check blast radius", "what would break if I change this", "refactoring safety analysis", or mentions keywords related to…
adamthewilliam/grepika
This skill should be used when the user asks to "check index status", "is the index healthy", "index diagnostics", "search index health", or mentions keywords related to verifying grepika search…
adamthewilliam/grepika
This skill should be used when the user asks to "investigate a bug", "trace an error", "debug this issue", "find where this error comes from", or mentions keywords related to error tracing and bug…
adamthewilliam/grepika
This skill should be used when the user asks to "learn this codebase", "give me a codebase overview", "onboard me to this project", "explain the architecture", or mentions keywords related to…
adamthewilliam/grepika
This skill should be used when the user asks to "map the architecture", "show module dependencies", "analyze coupling", "dependency graph", "how are modules connected", "module boundaries", or…
adamthewilliam/grepika
This skill should be used when the user asks to "compare files", "diff these files", "what changed between", "show differences between", "compare versions", or mentions keywords related to file…
Works with
Categories
This skill should be used when the user asks to "apply a pattern", "use a blueprint", "implement [pattern] from [source]", "what blueprints do I have", "list patterns", "adapt this pattern", or…. Apply Pattern is an agent skill from adamthewilliam/grepika. This skill should be used when the user asks to "apply a pattern", "use a blueprint", "implement [pattern] from [source]", "what blueprints do I have", "list patterns", "adapt this pattern", or mentions keywords related to applying previously extracted architectural patterns to their current project.
Apply Pattern fits situations like: asks to apply a pattern; use a blueprint; implement [pattern] from [source]; what blueprints do I have.
Run `npx skills add adamthewilliam/grepika --skill apply-pattern -a claude-code`. Or copy the skill folder (plugins/grepika/skills/apply-pattern in adamthewilliam/grepika) into .claude/skills/apply-pattern in your project. Claude Code loads it when a task matches its description.
Run `npx skills add adamthewilliam/grepika --skill apply-pattern -a codex`. Or copy the skill folder (plugins/grepika/skills/apply-pattern in adamthewilliam/grepika) into .agents/skills/apply-pattern 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 adamthewilliam/grepika --skill apply-pattern -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/apply-pattern, .gemini/skills/apply-pattern, .github/skills/apply-pattern and .opencode/skills/apply-pattern in your project.
SKILL.md names no scripts, command-line tools or credentials: Apply Pattern is instructions for the agent only. Our summary lists: Node.js. Its frontmatter pre-approves these tools: mcp__grepika__search, mcp__grepika__refs, mcp__grepika__outline, mcp__grepika__toc, mcp__grepika__get, mcp__grepika__structural_search, mcp__grepika__add_workspace, Bash, Read. Compatibility (from SKILL.md): Requires grepika MCP server..
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 notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
Apply Pattern 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.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Apply Pattern: Debugging Executions (n8n-io/n8n, 207k stars), Analyze Logs (activepieces/activepieces, 25k stars), Release (PrefectHQ/fastmcp, 28k stars) and Claude Code Skill (codeaashu/claude-code, 3.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
adamthewilliam (a GitHub user) maintains it in adamthewilliam/grepika, which has 138 GitHub stars. The repository holds 9 skills in this directory. The repository was last updated on August 12, 2026.
Source: adamthewilliam/grepika on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.