CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

check-form-logic

Check a fillable PDF form's hidden calculation logic against the other documents that describe the same rule (a spreadsheet, a user guide), before anyone automates, migrates or rebuilds the process. Runs the form's own scripts and the spreadsheet's own formulas on every possible input, traces each disagreement to the line that causes it, and ends with evidence and questions for the procedure owner. Use this whenever someone is about to build an automation, agent, workflow or new system on top of an existing fillable PDF or Excel calculator, asks whether a form "does what the spreadsheet/guide says", needs to audit a legacy form's scoring, weights, warnings or approval rules, or is migrating a paper or PDF process (for example to Power Platform, Dataverse or an agent platform), even if they don't say "audit" or "reconcile".

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

88%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-executed process skill: fully executable commands, a specified mapping format, explicit validate-and-rerun feedback loops around the batch reconciliation run, and a concrete output contract. Its minor costs are a trimmable motivational opening and an inline report template/helper reference that could be split into a bundled reference file.

Suggestions

Trim the two opening paragraphs to one or two sentences — the operational stance ('evidence, not rulings', never edit the originals) is load-bearing, but the narrative about drifting legacy processes can be compressed.

Move the step-7 report template and the step-4 helper-function reference into a bundled reference file (e.g. references/report-template.md) and link to them, keeping SKILL.md as the workflow overview.

State file-extension triggers (.pdf, .xlsx) in the description to lift trigger term coverage to the top anchor.

DimensionReasoningScore

Conciseness

The body is dense with non-obvious operational guidance ("A wrong mapping looks like a disagreement too", "Never describe a sampled result as 'every input'", owner questions must "Never mention scripts, fields, cells or formulas") and assumes Claude's competence throughout. Not 5: the two opening paragraphs (~90 words of motivation — "They drift apart, and nobody notices because each person only uses one of them") and a few framing sentences ("This is the one step that needs judgment about meaning") could be trimmed without losing operational content; not 3 because padding is minor and localized rather than 'some unnecessary explanation' spread across sections.

4 / 5

Actionability

Copy-paste-ready commands for each phase (`uv run python inspect_sources.py path/to/form.pdf path/to/calculator.xlsx [SHEET]`, `uv run python reconcile.py --mapping mappings/<form>.py --out runs/<form>/results.json`), a fully specified mapping-file shape (PDF, XLSX, SHEET, INPUTS, NAMES, CELLS, OUTPUTS, OUTPUT_LABELS), named helper functions with signatures (`load(mapping)`, `effective_weights(values, scores, ...)`, `conditions.explain(rows, mask, ...)`, `owner_questions.translate(co, text, terms)`), and a complete report template. Specific examples cover the common cases via the worked Field Visit example; not 4 because there is no pseudocode or missing key detail — every instruction maps to an executable command or file.

5 / 5

Workflow Clarity

Steps 0–7 are clearly sequenced (triage → inventory → mapping → exhaustive check → facts → guide claims → owner questions → report), and the batch operation has an explicit validation feedback loop: "Check the mapping before trusting the results. Run a small sample first... Correct the mapping and rerun until every remaining disagreement is explained by the logic, not by the mapping", plus a defined failure mode ("reconcile.py stops with an assertion... fix the mapping, don't edit the artifacts") and a coverage-sampling rule when combinations exceed a few million. Not 4: validation checkpoints are explicit with error-recovery loops, not merely present.

5 / 5

Progressive Disclosure

No bundle files exist (no references/, scripts/, or assets/ directories), and the body is well-sectioned with numbered headers and clearly signaled repo-tooling references (`reconcile.py`, `inspect_sources.py`, `facts.py`, `owner_questions.py`, `mappings/field_visit_risk.py`) that are one level deep. Not 5: the inline report template (~25 lines) and the helper-function reference list are content that could live in a reference file, and at ~125 lines the skill exceeds the 'under 50 lines, no external references needed' case that the rubric exempts; not 3 because structure is good and nothing is buried or nested.

4 / 5

Total

18

/

20

Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: concrete actions on both the what and when sides, explicit multi-scenario triggers including indirect phrasings, and a well-defined niche. The only gap is the absence of file-extension triggers and a few synonyms, which keeps trigger term quality just below the top anchor.

DimensionReasoningScore

Specificity

The description lists multiple concrete, verifiable actions — "Runs the form's own scripts and the spreadsheet's own formulas on every possible input", "traces each disagreement to the line that causes it", "ends with evidence and questions for the procedure owner" — with comprehensive coverage of the skill's behavior. Not 4: unlike a minor-gaps listing, every clause names a concrete action rather than a category, and nothing in the skill's operation is left unmentioned.

5 / 5

Completeness

Both halves are explicit: "what" is stated concretely up front (check hidden calculation logic against spreadsheet and guide, run scripts/formulas on every input, trace causes, produce evidence and owner questions) and "when" is a dedicated "Use this whenever..." clause with multiple concrete trigger scenarios (building automation/agents on a fillable PDF or Excel calculator, asking whether a form "does what the spreadsheet/guide says", auditing scoring/weights/warnings/approval rules, migrating to Power Platform/Dataverse). This matches the anchor-5 example pattern exactly; not 4 because the 'when' clause is fully explicit, not merely present.

5 / 5

Trigger Term Quality

Strong natural keyword coverage — "fillable PDF form", "spreadsheet", "user guide", "Excel calculator", "audit a legacy form's scoring, weights, warnings or approval rules", "migrating a paper or PDF process", plus indirect-trigger guidance ("even if they don't say 'audit' or 'reconcile'"). Not 5: anchor 5 expects synonyms AND file extensions; no ".pdf"/".xlsx" style extension triggers appear, and a few natural phrasings (e.g. "does the form match the spreadsheet") exist only as one quoted paraphrase.

4 / 5

Distinctiveness Conflict Risk

Clear niche — reconciling a fillable PDF form's embedded calculation logic against companion sources before automation — with triggers keyed to that scenario (legacy form audit, pre-automation check, paper/PDF process migration). Not 4: the trigger conditions are specific enough that generic PDF-extraction or Excel-analysis requests would not fire it; the only overlap (general 'automate this Excel process' asks) is an intended trigger, not a conflict.

5 / 5

Total

19

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

okwalerie/form-reconciler

Path

skills/check-form-logic/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.