SKILLEMALL.ai

BC markitdown

Converts heterogeneous documents and selected URIs to Markdown with Microsoft MarkItDown for text analysis, search, and LLM/RAG ingestion. Covers safe local conversion, streams, Office/PDF/data formats, batch workflows, plugins, vision OCR, Azure extraction, and the official MCP server.

K-Dense-AI/claude-scientific-skills Agent Skills author: K-Dense-AI MIT 11 files · 3 scripts body ≈ 2 889 tokens Open the sourcegithub.com↗ analyzed 12 h ago

Converts heterogeneous documents and selected URIs to Markdown with Microsoft MarkItDown for text analysis, search, and LLM/RAG ingestion.

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

GeneratorAzureWordGitHubExcelAI and agentstype and topics are labelled automatically from the skill text
JSON
Technical rating
B
91/100
safety, quality, tests
Safety 60%
99
Quality 40%
80
Run on models
none yet
Process rating
C
50/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
When it triggers w 12
20
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.
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

✓ Guard found no suspicious behaviour. 1 matches are attack strings quoted in this security skill's own documentation.

Files scanned: 11. 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")
  • note edit-residue the text marks something as outdated (lines 8): check that old rules are not kept next to new ones — the full check reads the text for contradictions

Process rating: all ten parameters 50/100

  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 6 mutating operations with no state check
  • 50Failures and branches. 0 branches, has a failure section
  • 60Tools and files. Uses tools (bash, web, python) that frontmatter does not declare
  • 100Steps. 27 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 2889 tokens
  • 100Progress reporting. Reports progress
  • 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

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

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