AC delaware-franchise-tax
File your Delaware annual franchise tax and annual report. Guides you through tax calculation (Authorized Shares and Assumed Par Value Capital methods), the eCorp portal filing process, and payment. For Delaware C-Corps (March 1 deadline) and LLCs/LPs/GPs (June 1 deadline). Use when user says "Delaware franchise tax," "annual report Delaware," "file franchise tax," or "eCorp portal."
As a process C 58/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- 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 · 4
✓ No critical or high findings
Medium and low: 4
-
low Secrets in code
secret-high-entropy-tokenreference/ecorp-portal-playwright-notes.md:31High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)- `grid…res` is **readonly** — it's auto-summed from per-class fields
quoted -
low Secrets in code
secret-high-entropy-tokenreference/ecorp-portal-playwright-notes.md:74High-entropy token-like string (may be an id, hash or a credential)| Issued shares (total, readonly) | grid…res |
-
low Secrets in code
secret-high-entropy-tokenreference/ecorp-portal-playwright-notes.md:75High-entropy token-like string (may be an id, hash or a credential)| Gross assets | grid…set |
-
low Secrets in code
secret-high-entropy-tokenreference/ecorp-portal-playwright-notes.md:76High-entropy token-like string (may be an id, hash or a credential)| Asset date | grid…ate |
Files scanned: 7. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
frontmatter-keyunknown frontmatter key "catalog_group" - note
frontmatter-keyunknown frontmatter key "catalog_order"
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
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 5 mutating operations with no state check
- 70Failures and branches. 7 branches
- 100Tools and files. No external tools needed
- 100Steps. 72 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2274 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
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
- +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
- +5Description quotes 4 example trigger phrases
- +3Description length 386: enough signal without eating the budget
- +4Structure: 19 headings
- +3Step-by-step instructions: 72 items
- +4Has examples (4 code blocks)
- +4Reference files are cited in the instructions (4 of 4)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 92.