AC abstract-logic-writer
write, critique, score, compare, and revise english academic abstracts for ai, systems, and computer science papers using computable symbolic rules, lightweight ontologies, and sentence-level discourse constraints. use when the task involves drafting an abstract from notes, repairing sentence-to-sentence logic, checking verb-noun compatibility such as growth versus development, scoring two abstract fragments with a formal rule-based metric, bootstrapping or downloading a domain ontology, removing generic ai phrasing such as em dashes or unlike, or generating deliberately flawed negative examples for teaching and comparison.
As a process C 64/100 · Has gaps — weak spots: inputs and preconditions, progress reporting
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 · 0
✓ No critical or high findings
Files scanned: 19. 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 64/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 50When it triggers. No condition that starts the skill
- 55Failures and branches. 1 branches
- 60Tools and files. Uses tools (bash, python) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 100Steps. 32 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1164 tokens
- 100Running it twice. No mutating operations
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)
- +4No input/output examples
- +2Single-language instructions
- +3Description length 631: enough signal without eating the budget
- +4Structure: 10 headings
- +3Step-by-step instructions: 32 items
- +3Output format is stated explicitly
- +4Reference files are cited in the instructions (5 of 5)
- +3All 3 scripts are documented
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 91.