gamussa/presenterm
Create terminal-based presentation slides using presenterm's markdown format with themes, diagrams, code highlighting, and more
92
90%
Does it follow best practices?
Impact
97%
2.15xAverage score across 5 eval scenarios
Passed
No known issues
Quality
Discovery
92%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description that clearly identifies the tool (presenterm), lists specific capabilities, and provides extensive trigger guidance. Its main weakness is the aggressive claim on generic presentation-related triggers like 'create a presentation' and 'slide deck in markdown', which could conflict with other presentation tools. The description is well-structured and uses appropriate third-person voice throughout.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete capabilities: 'terminal-based presentation slides', 'themes, code highlighting, images, column layouts, speaker notes'. Also mentions specific actions like 'create', 'convert content into presenterm format'. | 3 / 3 |
Completeness | Clearly answers both 'what' (create terminal-based presentation slides using presenterm's markdown format with themes, code highlighting, etc.) and 'when' (explicit 'Use this skill whenever...' clause with multiple trigger scenarios including edge cases). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms: 'presenterm', 'terminal slides', 'markdown slides', 'terminal presentation', 'markdown presentation', 'slide deck in markdown', 'create a presentation'. Covers both the tool name and generic phrasings users would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | While 'presenterm' is highly distinctive, the description also claims triggers like 'create a presentation' and 'markdown presentation' which could easily conflict with general presentation skills (e.g., PowerPoint/pptx creation). The conditional 'if they have used presenterm before' helps but still creates overlap risk. | 2 / 3 |
Total | 11 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality skill that provides comprehensive, actionable guidance for creating presenterm presentations. Its greatest strengths are the complete reference table of comment commands, the thorough speaker notes gotcha section with wrong/right examples, and the well-structured progressive disclosure to reference files. The only weakness is mild verbosity in a few sections (repeated warnings, the full PPTX conversion script) that could be trimmed without losing clarity.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient and covers a lot of ground, but some sections could be tightened. The PDF-to-PPTX conversion script and some explanatory text (e.g., 'Every business is becoming a real-time business' in the example) add bulk. The speaker notes section, while important, repeats the warning about colons/em dashes three times. However, most content earns its place given the complexity of presenterm's format. | 2 / 3 |
Actionability | Excellent actionability throughout — concrete YAML frontmatter examples, exact comment command syntax in a reference table, executable code blocks for PDF export and PPTX conversion, specific CLI commands, and a complete end-to-end example presentation. Everything is copy-paste ready with real syntax. | 3 / 3 |
Workflow Clarity | The skill clearly sequences the workflow: frontmatter → slides → content features → running/exporting. The speaker notes section includes an explicit validation step ('mentally scan for : and —') with wrong/right examples. The export workflow has clear steps with config file creation, and the troubleshooting note about diagram renderers showing as plain code provides error recovery guidance. | 3 / 3 |
Progressive Disclosure | Excellent progressive disclosure — the main file serves as a comprehensive but navigable overview, with four clearly signaled one-level-deep references (mermaid.md, d2.md, themes.md, design-patterns.md). The reference table at the top and inline links throughout make navigation easy. Content is appropriately split between the main skill and reference files. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
Reviewed
Table of Contents