Automated summary
Generates a publication-quality methodology diagram from a text file describing the method, using the PaperBanana MCP tool (with a CLI fallback).
Strengths
- Turns a plain text method description into a methodology figure with little manual work
- Uses a dedicated MCP tool with an explicit CLI fallback when the tool is unavailable
- Accepts a caption passed as an argument or asks the user to describe the intended figure
- Runs three iterations by default to refine the output
Limitations
- Requires the PaperBanana MCP tool or a locally installed paperbanana CLI
- Does not specify the exact output format or diagram styling options
- Assumes the input file already contains a usable textual description of the methodology
Use it when you need a ready methodology figure for a paper or report and already have the method described in text.
Avoid it when no structured method text exists, or when neither the PaperBanana MCP tool nor the CLI is available.
Security analysis
SafeThe skill only reads a text file and invokes a diagram-generation tool, with Bash narrowly scoped to `paperbanana *`. There are no destructive commands, no shell pipelines, no obfuscation, no credential access, and no attempts to disable safeguards. The only notable consideration is that file content is sent to a third-party generation service, which is inherent to the tool's stated purpose.
- •Reads an arbitrary user-supplied file path and forwards its contents to an external diagram-generation service (MCP tool or `paperbanana` CLI); this is the intended function but means file content leaves the local environment.
Examples
/generate-diagram method.txt "Overview of our encoder-decoder architecture"/generate-diagram docs/methodology.md — ask me for the caption and generate the figurepaperbanana generate --input method.txt --caption "Pipeline of our training procedure"user-invocable: true allowed-tools:
- mcp__paperbanana__generate_diagram
- Read
- "Bash(paperbanana *)"
Generate Diagram
Generate a publication-quality methodology diagram from a text file using PaperBanana.
Instructions
- Read the file at
$ARGUMENTS[0]to get the methodology text content. - If
$ARGUMENTS[1]is provided, use it as the figure caption. Otherwise, ask the user for a caption describing what the diagram should communicate. - Call the MCP tool
generate_diagramwith:source_context: the text content read from the filecaption: the figure captioniterations: 3 (default)
- Present the generated diagram to the user.
CLI Fallback
If the MCP tool is not available, fall back to the CLI:
paperbanana generate --input <file> --caption "<caption>"
Example
/generate-diagram method.txt "Overview of our encoder-decoder architecture"
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/generate-methodology-diagram-mm5t8bag/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/generate-methodology-diagram-mm5t8bag' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/generate-methodology-diagram-mm5t8bag/download' --output '.skill-downloads/generate-methodology-diagram-mm5t8bag/SKILL.md.part' && mv '.skill-downloads/generate-methodology-diagram-mm5t8bag/SKILL.md.part' '.skill-downloads/generate-methodology-diagram-mm5t8bag/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
This file does not provide a usable name/description header for this native procedure. It remains available to download and inspect; use the manual method below.
Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/generate-methodology-diagram-mm5t8bag/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
Supabase Docs Authoring
Documentation
Write, edit, and review Supabase documentation content including guides, tutorials, reference docs, and partials. Follow style guides and MDX/TOML validation rules.
Create Architecture Decision Record
Documentation
Create a new Architecture Decision Record with sequential numbering, register it in the AgentDB graph, and link related ADRs.
Plan update with deep research
Documentation
Updates a plan document by launching parallel subagents to analyze a topic across all compiler passes, then consolidates findings into the plan doc.