academic-plotting

Writing Community v1.0.0
Interpretation is structured for decision-making; original keeps the upstream SKILL.md unchanged.

Decide Fit First

  • Core job: Generates publication-quality figures for ML papers from research context. Given a paper section or description, extracts system…
  • Best fit: Use it when the task has reusable inputs, steps, and validation criteria rather than a one-off answer.
  • Avoid forcing it: If the source lacks commands, platform support, or external-service evidence, keep those fields unknown instead of guessing.

Design Intent

  • Structure: The skill is organized around “When to Use Which Workflow”, “Step 0: Context Analysis & Extraction”, “Extraction Workflow”, “Auto-Detection Examples”, showing how the author expects the agent to judge fit, collect context, and produce verifiable output.
  • Trigger evidence: Prioritize the author’s wording around when to use it, what context to collect, and what output shape to produce.
  • Evidence boundary: Author text states facts, repository files prove commands and paths, and Fluxly only adds fit, limits, and usage judgment.

How To Use It

  • Inputs: Provide target material, scope, expected result, forbidden changes, and validation method.
  • Invocation: Name academic-plotting directly; if the source includes slash commands, start with the command and then add task context.
  • Validation: Start small and check whether the result follows “When to Use Which Workflow / Step 0: Context Analysis & Extraction / Extraction Workflow” before expanding.

Boundaries And Review

  • Dependencies: Prepare Gemini API keys before running a full task.
  • Permissions: Declared permissions include read / write / shell-exec / env-read; ask the agent to state file, command, and rollback boundaries before acting.
  • Quality bar: A useful result names the deliverable, evidence, and next action. Generic prose means the task needs tighter context.
Fluxly profile Author and license come from source; runtime, permissions, and network are Fluxly detections or estimates
Fluxly category
Writing · Academic Writing · Visualization · Matplotlib
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
98 / 100 · heuristic scan, not runtime safety proof
Author / version / license
@Orchestra-Research · v1.0.0 · MIT
Fluxly token estimate
Moderate
Fluxly setup estimate
Manual integration
External API key
Required · Gemini
Detected OS requirements
macOS · Linux · Windows
Runtime requirements
Node.js · Python
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
  • Env read
Detected network behavior
External requests
Install commands
None (reference only)

Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.

Heads up: allowed-tools 包含 11 项,权限面较宽。

Output preview academic-plotting.preview
# Auto-Detection Examples

**Context → Diagram**: "Our system has a Planner, Executor, and Verifier. Planner sends plans to Executor, Executor returns results to Verifier, Verifier feeds back to Planner on failure." → 3 entities, cycle layout, dashed feedback arrow → **Workflow 1 (Gemini)** **Data → Chart**: "GPT-4: MMLU 86.4, HumanEval 67.0. Ours: 88.1, 71.2. Llama-3: 79.3, 62.1." → 3 methods × 2 benchmarks → **Workflow 2 (grouped bar)**, highlight "Ours" in coral ---

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.