Menü
This skill should be used when the user wants to create a visual sketch, diagram, or mind map from captured content like articles, videos, or blips. Enables creating Excalidraw visualizations from jot captures.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
| name | sketch-from-capture |
| description | This skill should be used when the user wants to create a visual sketch, diagram, or mind map from captured content like articles, videos, or blips. Enables creating Excalidraw visualizations from jot captures. |
| version | 1.0.0 |
When a user captures content and wants to visualize it, use the /sketch command from the sketch-note plugin.
Use this skill when the user mentions:
Extract the key information needed for visualization:
When visualizing video content:
Visualization approach:
When visualizing article content:
Visualization approach:
When visualizing tech radar blips:
Visualization approach:
After extracting content, invoke the sketch command:
/sketch --mode custom "{extracted content description}"
Example workflow:
User: "capture https://youtube.com/watch?v=abc123 and visualize it"
First, capture the video using jot capture:
Extract key concepts:
Create visualization:
/sketch --mode custom "REST API tutorial flow: Setup → Routing → Middleware → Authentication → Error Handling → Testing. Key concepts: Express.js framework, JWT tokens, middleware pattern"
Link the sketch to the capture note (both in workbench)
Both captures and sketches are saved to the shared workbench:
${workbench_path}/notes/{type}/${workbench_path}/sketches/This makes it easy to find related content together.
When creating a sketch from captured content, include a reference in the sketch description:
This maintains traceability between captures and their visualizations.
Review and clean up commits before pushing. Uses planner/executor split: reads commits inline, authors final messages in saved style, replays via `git rebase --exec` with GIT_EDITOR=true so no editor opens. Detects logical clusters of granular TDD commits and proposes collapsing them into one logical commit. Auto-amends drifted subjects on revalidation. Activates on: "review commits", "clean up commits", "prep for push", "squash these commits", "finalize commits", "merge branch to main", "clean up my commits before pushing", "review before push".
Validate commits before pushing. Runs six deterministic checks: clean worktree, tests pass, no AI co-author leaks (Claude, Anthropic, GPT, OpenAI, Copilot), no conflict markers, no squash/fixup residue, and subject lines conform to the configured style (classic or conventional). Activates on: "validate commits", "check commits before push", "any AI leaks", "check for co-author", "are my commits clean", "validate before pushing", "check commits".
Triggers when user wants to PERFORM a git commit action. Activates on phrases like "commit these changes", "commit this", "let's commit", "make a commit", "create a commit", "commit my work", "commit the changes", "time to commit", "ready to commit", "commit what I've done", "save my changes" (git context), "commit for me", "do the commit", "commit now", "go ahead and commit", "please commit", "can you commit", "would you commit"
Provides educational guidance on writing good git commit messages. Activates when users ASK QUESTIONS about commit message formats, styles, conventional commits, classic commits, atomic commit principles, or git best practices. Does NOT activate when users want to PERFORM a commit (use the commit-action skill instead).
Initialize and manage Nix flake development environments with auto-detection and security tooling
Guardrail for efficient refactoring. IDEs use AST-based semantic refactoring (instant, atomic, accurate). AI uses text-based pattern matching (slower, sequential, error-prone for structural changes). This skill provides decision criteria for when to delegate to IDE vs proceed with AI. Consult before: renames across files, moving packages, changing signatures, extracting interfaces, or any multi-file coordinated structural change.