AF easylink-easydoc-extract
Use when tasks need EasyLink extraction API to extract structured fields from documents. Trigger for requests about POST /v1/easydoc/extract and GET /v1/easydoc/extract/{task_id}, selecting mode (easydoc-extract, easydoc-extract-flash, bl-extract, occ-extract), customizing extracted fields via json_schema, using custom prompts, and handling async polling until SUCCESS or FAILED.
Trigger for requests about POST /v1/easydoc/extract and GET /v1/easydoc/extract/{taskid}, selecting mode (easydoc-extract, easydoc-extract-flash, bl-extract…
As a process F 45/100 · Will not run — References files that are not bundled: references/easydoc-extract-api.md, scripts/easydoc_extract.py
How to improve
- The text references files that are not there: add them or drop the references.
- 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 · 0
✓ No critical or high findings
Files scanned: 0. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: references/easydoc-extract-api.md - warning
missing-refreference to a missing file: scripts/easydoc_extract.py
Process rating: all ten parameters 45/100
- 0Tools and files. 2 referenced file(s) missing: references/easydoc-extract-api.md, scripts/easydoc_extract.py
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 1 mutating operations with no state check
- 40Consistency. Frontmatter name (easylink-easydoc-extract) differs from the folder (easydoc-extract)
- 55Failures and branches. 1 branches
- 60Result and completion. Output format stated, no completion criterion
- 100Steps. 36 steps
- 100Execution cost. Instruction body is 1285 tokens
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)
- +1No license
- +2Single-language instructions
- +3Description length 381: enough signal without eating the budget
- +4Structure: 10 headings
- +3Step-by-step instructions: 36 items
- +3Output format is stated explicitly
- +4Has examples (8 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 78.