skills/generate-diagram/SKILL.md
Use this skill when creating a methodology diagram from research text. Triggers on "make a diagram", "visualize this methodology", "diagram this process", or "generate a figure from this paper". Applies to methodology descriptions, process flows, and research paper sections. Do NOT use for scoring existing diagrams (use evaluate-diagram) or plotting data from CSV/JSON (use generate-plot).
npx skillsauth add dtsong/my-claude-setup generate-diagramInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Generate a publication-quality methodology diagram from a text file using PaperBanana.
$ARGUMENTS[0] — path to the methodology text file$ARGUMENTS[1] — figure caption (prompted if not provided)~/Desktop/PaperBanana/ contentsBefore using $ARGUMENTS[0] in file operations:
../, null bytes, or shell metacharacters (; | & $ `)$ARGUMENTS[0] to get the methodology text content.$ARGUMENTS[1] is provided, use it as the figure caption. Otherwise, ask the user for a caption describing what the diagram should communicate.paperbanana:generate_diagram with:
source_context: the text content read from the filecaption: the figure captioniterations: 3 (default)~/Desktop/PaperBanana folder (including any subfolders) to show the full iterative history — previous versions, metadata, intermediate outputs, etc. # SECURITY: PaperBanana's designated output directory; contains only generated artifactsPresent the generated diagram with a summary of parameters used (caption, iterations) and the full contents listing of ~/Desktop/PaperBanana/.
If the MCP tool is not available, fall back to the CLI:
paperbanana generate --input <file> --caption "<caption>"
/generate-diagram method.txt "Overview of our encoder-decoder architecture"
development
Use when planning implementation steps, deciding commit format, or structuring development approach. Provides brainstorm-plan-implement flow with conventional commits. Triggers on 'how should I approach this', 'commit format'.
development
Security audit checklist for web applications. Use when reviewing, auditing, or hardening a web app's security posture. Covers rate limiting, auth headers, IP blocking, CORS, security middleware, input validation, file upload limits, ORM usage, and password hashing. Triggers on requests like "review security", "harden this app", "security audit", "check for vulnerabilities", or when building/reviewing API endpoints.
development
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".
development
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.