SKILLEMALL.ai
GitHub ↗ RU Sign in

CF anydoc

Convert Word (.doc/.docx/.docm), PowerPoint (.ppt/.pps/.pot/.pptx/.pptm/.ppsx/.ppsm), Excel (.xls/.xlsx/.xlsm/.xlsb), OpenDocument (.odt/.ods/.odp), RTF, EPUB, CSV, and PDF documents to clean GitHub-Flavored Markdown locally with the Any Doc CLI (npx -y @firecrawl/anydoc@0.2.4): headings, GFM tables, slide structure, and footnotes in one pass. Use when a task needs the contents of an office document, spreadsheet, presentation, ebook, or PDF you cannot read directly. Do not use for generating, editing, or validating documents (use documents), for ebook packaging (use epub). For scanned or image-only PDFs, use hosted OCR only when the user explicitly authorizes whole-document upload; otherwise route to local OCR tooling.

magnus919/agent-skills Agent Skills author: magnus919 MIT 14 files · 2 scripts body ≈ 3 403 tokens Open the sourcegithub.com↗ analyzed 27 h ago

Convert Word (.doc/.docx/.docm), PowerPoint (.ppt/.pps/.pot/.pptx/.pptm/.ppsx/.ppsm), Excel (.xls/.xlsx/.xlsm/.xlsb), OpenDocument (.odt/.ods/.odp), RTF…

As a process F 61/100 · Will not run — References files that are not bundled: scripts/anydoc

GeneratorWordExcelPowerPointGitHubData and analyticstype 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
89/100
safety, quality, tests
Safety 60%
90
Quality 40%
87
Run on models
none yet
Process rating
F
61/100
Will not run
References files that are not bundled: scripts/anydoc
Tools and files w 18
0
Inputs and preconditions w 11
0
Progress reporting w 2
0
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.

Concealment 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 tells the agent to hide things from you: not to show errors, not to mention actions, to report differently from what was done. You lose the ability to see what the agent really did.

For the author

Transparency beats a smooth answer. If the goal is to hide technical noise, ask the agent to "summarise briefly", not to "not mention".

Broad scope 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 asks for more than the task needs: broad tool access, credential environment variables, binaries. Every extra permission widens the damage from a mistake or a compromise.

For the author

Narrow allowed-tools and the variable list to the minimum; replace binaries with readable sources or scripts.

How to improve

  1. The text references files that are not there: add them or drop the references.
For the model run — optional
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 2

✓ No critical or high findings

Medium and low: 2
  • medium Concealment en-hide-from-user references/errors.md:148
    Instruction to hide actions from the user (quoted — discussed, not commanded)
    Do not fabricate the document's content or silently upload it.
    quoted
  • medium Broad scope meta-broad-allowed-tools SKILL.md:1
    Broad tool permissions pre-approved: Bash
    allowed-tools: Bash Read

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

Against the Agent Skills spec

  • warning missing-ref reference to a missing file: scripts/anydoc
  • note edit-residue the text marks something as outdated (lines 57, 125, 185, 192): check that old rules are not kept next to new ones — the full check reads the text for contradictions

Process rating: all ten parameters 61/100

Will not run. References files that are not bundled: scripts/anydoc
  • 0Tools and files. 1 referenced file(s) missing: scripts/anydoc
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Progress reporting. Says nothing while it works
  • 30Running it twice. 5 mutating operations with no state check
  • 60Result and completion. Output format stated, no completion criterion
  • 100Steps. 17 steps
  • 100When it triggers. States when to use and when not to
  • 100Failures and branches. 2 branches, has a failure section
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 3403 tokens
  • low The response is described with custom markup (9 tags): a typed call is more reliable
  • low No test case covers injection arriving through data

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
  • -31 of 1 scripts are never mentioned in SKILL.md
  • +2Single-language instructions
  • +4Description says when NOT to use the skill
  • +3Description length 728: enough signal without eating the budget
  • +4Structure: 10 headings
  • +3Step-by-step instructions: 17 items
  • +3Output format is stated explicitly
  • +4Has examples (3 code blocks)
  • +4Reference files are cited in the instructions (6 of 6)
  • +1License stated

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