SKILLEMALL.ai
GitHub ↗ RU Sign in

AB eas-update-insights

Check the health of published EAS Updates: crash rates, install/launch counts, unique users, payload size, and the split between embedded and OTA users per channel.

sickn33/agentic-awesome-skills Agent Skills author: sickn33 MIT 4 files body ≈ 2 740 tokens Open the sourcegithub.com↗ analyzed 2 d ago

Check the health of published EAS Updates: crash rates, install/launch counts, unique users, payload size, and the split between embedded and OTA users per…

As a process B 74/100 · Nearly there — weak spots: running it twice, progress reporting

ProcedureData and analyticstype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
A
97/100
safety, quality, tests
Safety 60%
100
Quality 40%
93
Run on models
none yet
Process rating
B
74/100
Nearly there
Progress reporting w 2
0
Running it twice w 4
30
Failures and branches w 10
50
the three weakest of ten parameters · all ten

The same skill appears in 2 more places: agentic-awesome-skills, agentic-awesome-skills

How to improve

    For the model run — optional
    • 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: 4. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    • note frontmatter-key unknown frontmatter key "risk"
    • note frontmatter-key unknown frontmatter key "source"
    • note frontmatter-key unknown frontmatter key "source_repo"
    • note frontmatter-key unknown frontmatter key "source_type"
    • note frontmatter-key unknown frontmatter key "date_added"
    • note frontmatter-key unknown frontmatter key "license_source"
    • note edit-residue the text marks something as outdated (lines 109): check that old rules are not kept next to new ones — the full check reads the text for contradictions

    Process rating: all ten parameters 74/100

    • 0Progress reporting. Says nothing while it works
    • 30Running it twice. 11 mutating operations with no state check
    • 50Failures and branches. 0 branches, has a failure section
    • 60Tools and files. Uses tools (bash, node) that frontmatter does not declare
    • 60Result and completion. Output format stated, no completion criterion
    • 70Inputs and preconditions. Inputs and preconditions are listed
    • 100Steps. 28 steps
    • 100When it triggers. States when to use and when not to
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 2740 tokens
    • low 10 top-level sections: this looks like several domains in one skill
    • low The response is described with custom markup (13 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
    • +2Single-language instructions
    • +4Description says when NOT to use the skill
    • +3Description length 164: enough signal without eating the budget
    • +4Structure: 23 headings
    • +3Step-by-step instructions: 28 items
    • +3Output format is stated explicitly
    • +4Has examples (9 code blocks)
    • +4Reference files are cited in the instructions (2 of 2)
    • +1License stated

    Quality base 70; lint remarks subtract, signals add up to 100. Result: 93.