SKILLEMALL.ai
GitHub ↗ RU Sign in

CA present-paper

Academic presentation preparation — paper-driven (journal club, grand rounds, seminar) and lecture/teaching decks (course material, workshop slides, conference talks). Analyzes source material, finds supporting references, drafts audience-adapted speaker scripts, generates or augments PPTX with speaker notes, and prepares Q&A.

Aperivue/medsci-skills Agent Skills author: Aperivue MIT 47 files · 30 scripts body ≈ 13 189 tokens Open the sourcegithub.com↗ analyzed 32 h ago

Academic presentation preparation — paper-driven (journal club, grand rounds, seminar) and lecture/teaching decks (course material, workshop slides…

As a process A 80/100 · Runs to the end — weak spots: execution cost, progress reporting

AnalyzerPowerPointWriting and documentsResearchPersonal productivitytype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
C
88/100
safety, quality, tests
Safety 60%
100
Quality 40%
70
Run on models
none yet
Process rating
A
80/100
Runs to the end
Progress reporting w 2
0
Execution cost w 6
40
Result and completion w 14
60
the three weakest of ten parameters · all ten

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
  2. The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
For the model run — optional
  • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 0

✓ No critical or high findings

Files scanned: 40. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • warning body-long SKILL.md body ≈ 13189 tokens (recommended < 5000); move details to references/
  • note frontmatter-key unknown frontmatter key "triggers"
  • note frontmatter-key unknown frontmatter key "tools"
  • note edit-residue the text marks something as outdated (lines 740): check that old rules are not kept next to new ones — the full check reads the text for contradictions

Process rating: all ten parameters 80/100

  • 0Progress reporting. Says nothing while it works
  • 40Execution cost. Instruction body is 13189 tokens: crowds the task out of the window
  • 60Result and completion. Output format stated, no completion criterion
  • 70When it triggers. States when to use, but not when not to
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 85Steps. 101 steps, 3 vague phrases
  • 100Tools and files. Tools declared in frontmatter
  • 100Failures and branches. 5 branches, has a failure section
  • 100Consistency. Name and required fields are in place
  • 100Running it twice. Mutating operations check current state
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
  • low 12 top-level sections: this looks like several domains in one skill
  • high The skill tells the model to perform an irreversible action with no human approval
  • low The response is described with custom markup (10 tags): a typed call is more reliable

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +5Description has no quoted example phrases that should trigger the skill
  • +4Description does not say when NOT to use the skill (false activations)
  • +1No license
  • +2Single-language instructions
  • +3Description length 328: enough signal without eating the budget
  • +4Structure: 54 headings
  • +3Step-by-step instructions: 101 items
  • +3Output format is stated explicitly
  • +4Has examples (25 code blocks)
  • +4Reference files are cited in the instructions (7 of 8)
  • +3All 11 scripts are documented

Quality base 70; lint remarks subtract, signals add up to 100. Result: 70.