SKILLEMALL.ai
GitHub ↗ RU Sign in

AC 2slides

AI-powered presentation generation using 2slides API. Create slides from text content, match reference image styles, or summarize documents into presentations. Use when users request to "create a presentation", "make slides", "generate a deck", "create slides from this content/document/image", or any presentation creation task. Supports theme selection, multiple languages, and both synchronous and asynchronous generation modes.

modbender/skill-library-mcp Agent Skills author: modbender MIT 13 files body ≈ 4 673 tokens Open the sourcegithub.com↗ analyzed 3 d ago

AI-powered presentation generation using 2slides API.

As a process C 54/100 · Has gaps — weak spots: result and completion, when it triggers, consistency

IntegrationWordWriting and documentsAI and agentstype and topics are labelled automatically from the skill text
Runs in: OpenClaw 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) Goose OpenCode
JSON
Technical rating
A
95/100
safety, quality, tests
Safety 60%
95
Quality 40%
96
Run on models
none yet
Process rating
C
54/100
Has gaps
Result and completion w 14
0
Progress reporting w 2
0
When it triggers w 12
20
the three weakest of ten parameters · all ten

What is at stake

Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.

Dangerous commands medium severity

Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.

If you install

The skill contains commands that delete files, rewrite disks or execute code fetched from the network. The agent may run them without asking if it believes the instructions require it.

For the author

Replace destructive commands with safe equivalents that ask for confirmation, scope them to one folder, and stop piping curl into a shell: pin a version and a checksum.

How to improve

    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 · 1

    ✓ No critical or high findings

    Medium and low: 1
    • medium Dangerous commands cmd-shell-rc README.md:83
      Writes to a shell startup file
      echo 'export SLID…KEY="your_api_key_here"' >> ~/.zshrc

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

    Against the Agent Skills spec

    ✓ No remarks against the Agent Skills spec

    Process rating: all ten parameters 54/100

    • 0Result and completion. Does not say what the result is
    • 0Progress reporting. Says nothing while it works
    • 20When it triggers. No condition that starts the skill
    • 30Running it twice. 14 mutating operations with no state check
    • 40Consistency. Frontmatter name (2slides) differs from the folder (2slides-skills)
    • 50Failures and branches. 0 branches, has a failure section
    • 70Inputs and preconditions. Inputs and preconditions are listed
    • 70Execution cost. Instruction body is 4673 tokens
    • 85Steps. 154 steps, 2 vague phrases
    • 100Tools and files. No external tools needed
    • low 13 top-level sections: this looks like several domains in one skill

    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

    • +4Description does not say when NOT to use the skill (false activations)
    • +3Output format is not stated: the model decides each time
    • +1No license
    • +2Single-language instructions
    • +5Description quotes 4 example trigger phrases
    • +3Description length 431: enough signal without eating the budget
    • +4Structure: 38 headings
    • +3Step-by-step instructions: 154 items
    • +4Has examples (28 code blocks)
    • +4Reference files are cited in the instructions (3 of 3)
    • +3All 6 scripts are documented

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