SKILLEMALL.ai
GitHub ↗ RU Sign in

BC liteparse

Local document and PDF parsing that returns spatial text with bounding boxes. Use for extracting text from PDFs, DOCX, Office files, and images; running OCR on scans; producing layout-preserved JSON for RAG; batch-ingesting folders of papers; or rendering pages to PNG for multimodal agents. Distinguishing capabilities are spatial text boxes, Markdown, page raster output, and local parsing with optional custom HTTP OCR.

K-Dense-AI/claude-scientific-skills Agent Skills author: K-Dense-AI MIT 7 files · 1 script body ≈ 2 866 tokens Open the sourcegithub.com↗ analyzed 11 h ago

Local document and PDF parsing that returns spatial text with bounding boxes.

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

ProcedureWordGitHubAI and agentstype 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
B
92/100
safety, quality, tests
Safety 60%
94
Quality 40%
90
Run on models
none yet
Process rating
C
58/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

What is at stake

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

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

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

    ✓ No critical or high findings

    Medium and low: 2
    • medium Broad scope meta-broad-allowed-tools SKILL.md:1
      Broad tool permissions pre-approved: Bash
      allowed-tools: Read Write Edit Bash
    • low Obfuscation obf-base64-blob references/api_reference.md:229
      Long base64-looking blob (detector / deny-list definition)
      Sources: [Python API](https://github.com/run-llama/liteparse/blob/d3a7…f76/packages/python/README.md), [Node API](https://github.com/run-llama/liteparse/blob/d3a79177b9
      detector

    Files scanned: 7. 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 58/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. 2 mutating operations with no state check
    • 50Failures and branches. 0 branches, has a failure section
    • 100Tools and files. Tools declared in frontmatter
    • 100Steps. 22 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 2866 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
    • -2localhost URLs: will not work for another user
    • +2Single-language instructions
    • +3Description length 422: enough signal without eating the budget
    • +4Structure: 25 headings
    • +3Step-by-step instructions: 22 items
    • +4Has examples (21 code blocks)
    • +4Reference files are cited in the instructions (5 of 5)
    • +3All 1 scripts are documented
    • +1License stated

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