AB aistro
Professional astrology consultation skill providing personalized readings and reports. Use when the user asks about astrology, horoscopes, zodiac signs, birth charts, natal charts, star signs, planetary influences, compatibility, synastry, moon phases, daily/weekly/monthly horoscope predictions, or any astrology-related question. Supports five modes: (1) Chat — conversational astrology Q&A, (2) Natal Report — birth chart analysis by planet, (3) Predict Report — daily horoscope with topic breakdowns, (4) Synastry Report — compatibility analysis between two people, (5) Moon Phase Report — lunar influence reading. Trigger keywords: astrology, horoscope, zodiac, birth chart, natal chart, compatibility, compatible, synastry, moon phase, star sign, planetary transit, fortune, 占星, 星盘, 本命盘, 运势, 合盘, 月相, 合不合, 配不配.
As a process B 71/100 · Nearly there — 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: 11. 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 71/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 60Tools and files. Uses tools (bash, node) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 70When it triggers. States when to use, but not when not to
- 100Steps. 47 steps
- 100Failures and branches. 9 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2032 tokens
- 100Running it twice. No mutating operations
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low The response is described with custom markup (3 tags): a typed call is more reliable
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)
- +3Description length 815: 120–800 characters recommended
- +1No license
- +2Single-language instructions
- +4Structure: 20 headings
- +3Step-by-step instructions: 47 items
- +3Output format is stated explicitly
- +4Has examples (4 code blocks)
- +4Reference files are cited in the instructions (4 of 4)
- +3All 3 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 91.