generate-plot
Generate Plot
Generate a publication-quality statistical plot from a data file using PaperBanana.
Inputs
- Required:
$ARGUMENTS[0]— path to the data file (CSV or JSON) - Optional:
$ARGUMENTS[1]— plot intent description (prompted if not provided)
Scope Constraints
- Read ONLY the user-specified data file
- Do NOT read, write, or reference home directory dotfiles (~/.ssh, ~/.env, etc.)
- Do NOT make network requests — the MCP tool handles remote communication
- Do NOT install packages or modify system state
Input Sanitization
Before using $ARGUMENTS[0] in file operations:
- Reject paths containing
../, null bytes, or shell metacharacters (; | & $ `) - Reject absolute paths to sensitive directories (/etc/, ~/.ssh/, ~/.aws/, ~/.gnupg/)
- Verify the file exists before reading
Procedure
- Read the file at
$ARGUMENTS[0]to get the data content. - If the file is CSV, convert it to a column-keyed JSON dictionary (each key is a column name, each value is a list of values). If the file is already JSON, use the content directly.
- If
$ARGUMENTS[1]is provided, use it as the plot intent description. Otherwise, ask the user what kind of plot they want and what it should show. - Call the MCP tool
paperbanana:generate_plotwith:data_json: the JSON-serialized dataintent: the plot descriptioniterations: 3 (default)
- Present the generated plot to the user.
Output Format
Present the generated plot with a summary of parameters used (data source, intent, iterations).
CLI Fallback
If the MCP tool is not available, fall back to the CLI:
paperbanana plot --data <file> --intent "<intent>"
Example
/generate-plot results.csv "Bar chart comparing model accuracy across datasets"
More from dtsong/my-claude-setup
web-security-hardening
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.
26web-design-guidelines
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".
8soc-security-skills
>
6vercel-react-best-practices
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.
3code-search
Fast codebase searches using grep/glob. Triggers on "find", "search", "where is", "grep for".
2prompt wizard
Interactive wizard to craft effective prompts using Claude Code best practices
2