Real Skill packageSource verifiedClawHub registry

evaluate-skill

Measure a skill's reliability — run it k times for a pass@k score, design or interpret its eval, or compare it against the base agent. Use when the user wants to run, design, or interpret a skill's eval, or write an .eval.yaml spec.

Identity and source

Publisher attributionEmrick Donadeiregistry owner unverified by skillvetai
Functional categoryAgent Engineering, Security & Governanceautomatically inferred · 64% rule confidence
Package forminstruction bundle4 recorded files
Canonical sourceClawHub registryclawhub:edonadei:evaluate-skill
Open canonical source ↗

Platform declarations

These states come from the source or distribution context. None of the entries below are SkillVetAI compatibility test results.

OpenClawnative officialProvenance: registry distribution

Independent structural checks

These checks parse the fixed package against dated platform rules. They do not execute the Skill or verify task behavior.

Claude Codepasses structure
Checker 0.1.0 · agent-skills-2026-08-13+claude-code-docs-2026-08-13 · 9/25/2026.claude/skills/evaluate-skill

Runtime, accounts, dependencies, permissions, network behavior and task quality remain untested.

OpenAI Codexpasses structure
Checker 0.1.0 · agent-skills-2026-08-13+codex-docs-2026-08-13 · 9/25/2026.agents/skills/evaluate-skill

Runtime, accounts, dependencies, permissions, network behavior and task quality remain untested.

OpenClawpasses structure
Checker 0.1.0 · agent-skills-2026-08-13+openclaw-docs-2026-08-13 · 9/25/2026skills/evaluate-skill

Runtime, accounts, dependencies, permissions, network behavior and task quality remain untested.

Installation and inspection

This command is recorded from the source ecosystem and resolves the registry's latest release. The fixed release shown on this page should be inspected before adoption.

clawhub install @edonadei/evaluate-skill
clawhub inspect @edonadei/evaluate-skill --version 1.0.14

Security evidence

SkillVetAI static result: no findings detected

This automated, non-executing scan is bound to this release hash. It is not a safety certification and may contain false positives or false negatives.

Status
completed
Coverage
full text content
Files
4 / 4 inspected as text
Checked
9/25/2026, 5:16:11 PM
Scanner
0.1.3
Policy
1.0.3
3 inferred permission indicators
  • shell execution — automatically inferred
  • network access — automatically inferred
  • filesystem write — automatically inferred
2 dependency and API indicators
  • api: clawhub.ai
  • api: mcp.example.com
External clawhub result: clean

This is registry-supplied evidence for the recorded release, not an independent SkillVetAI scan. Check the canonical source for the full report, scanner versions, scope, and current moderation state.

Evidence checked
9/25/2026, 4:09:29 PM
Release binding
Matches this record
  • vt: clean
  • skillspector: suspicious
  • llm: clean

Recorded files

The catalog stores hashes and an inventory summary for change detection. It does not republish the package contents.

Package content hashsha256:2dad0e1a377430e6080891d630bcbbe30ea2da5b7d920f27cc15a2c17aaa906d
Show up to 4 recorded paths
  • evaluate-skill.eval.yaml
  • REFERENCE.md
  • skill-card.md
  • SKILL.md

Source changelog

### Changed - Clean-up from the 1.0.13 that added way too much files. - Built around four questions, each with its own place to fix: does the skill fire (`description`), does it work (body), does it earn its place (the tasks), does it hold across edits. - New workflow order: run the control (`--ablate <skill>`) once, before editing the skill, and keep it. After each edit, compare against the previous full run as well as the control, because a worse skill can still beat the control. - New diagnosis table traces each failure to its fix: setup errors, unusable attempts, `cheat`, a skill that didn't fire, an extra skill that fired, a skill that fired but failed, and tasks that pass without the skill. - Specs it writes put `activates:` on every execution task (plus any skill the task delegates to), never name the skill in a prompt, and include at least one trigger probe. - Now owns writing a…

Release security diff

mediumCompared fixed releases 1.0.12 and 1.0.14; 0 finding and 0 permission indicators were added.

Both fixed releases were scanned under the current scanner and policy, so finding, permission and dependency changes are available.

Change reasons and limitations
  • permission surface changed
  • dependency surface changed
  • file surface changed
  • content hash changed

Observed release history

These older immutable releases were observed by prior successful syncs. They remain recorded when a newer release becomes current.

1.0.128/29/2026sha256:522f41fc0084022791622e6a0fe46a4f7882665194dac578df8c07500f53b104