AC hadith-verifier
Verify hadith authenticity before publishing any Islamic content. Checks hadith text against major hadith collections (Bukhari, Muslim, Tirmidhi, Abu Dawud, Nasai, Ibn Majah, Malik) via open-source hadith API. Use when: (1) a user asks to verify a hadith, (2) before publishing any content that quotes a hadith, (3) when building Islamic content that references prophetic sayings, (4) when another agent or user claims a hadith is from a specific source. Triggers: "verify hadith", "check hadith", "is this hadith authentic", "hadith verification", "authenticate hadith", "search hadith", "hadith checker", "تحقق من حديث", "صحة الحديث".
Verify hadith authenticity before publishing any Islamic content.
As a process C 53/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 · 0
✓ No critical or high findings
Files scanned: 5. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Nested mappings are not allowed in compact mappings at line 2, column 14: description: Verify hadith authenticity before publishing any Islamic content. … ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value
Process rating: all ten parameters 53/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 100Tools and files. No external tools needed
- 100Steps. 16 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 822 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
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- -216 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +5Description quotes 9 example trigger phrases
- +3Description length 636: enough signal without eating the budget
- +4Structure: 17 headings
- +3Step-by-step instructions: 16 items
- +4Has examples (4 code blocks)
- +3All 2 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 80.