.claude/skills/grill-skillRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
Build and harden a skill with evals — interview to design its eval tasks, then run, measure, and iterate. Use when the user wants to create or improve a skill's eval, or run the create → test → improve loop for a skill.
These states come from the source or distribution context. None of the entries below are SkillVetAI compatibility test results.
These checks parse the fixed package against dated platform rules. They do not execute the Skill or verify task behavior.
.claude/skills/grill-skillRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
.agents/skills/grill-skillRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
skills/grill-skillRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
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/grill-skillclawhub inspect @edonadei/grill-skill --version 1.0.11This automated, non-executing scan is bound to this release hash. It is not a safety certification and may contain false positives or false negatives.
eval (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.
The catalog stores hashes and an inventory summary for change detection. It does not republish the package contents.
sha256:4f91bbb620d0eeecf11e7af457e9b2fb7b15f41f3ee90278917d4748aa468153grill-skill.eval.yamlREFERENCE.mdskill-card.mdSKILL.md### Changed - The interview now covers triggering: it asks which skills yours could be confused with, adds a neighbour probe for each, and always proposes a silence probe. - Generated tasks put `activates:` on every execution task and never name the skill in the prompt, so a run can tell a `description` failure from a body failure. - New Phase 4: run the control (`--ablate <skill>`) before editing the skill. A task that passes without the skill gets sharpened before any iteration. - New Phase 5: each failure is traced to its fix (`description`, body, task, or setup). After each edit, compare against the previous full run and against the kept control. - Warns that the harness is single-shot: for a skill that asks before acting, tasks judge the first turn. - Now focused on the interview (helping you decide what to test). Writing a spec whose tasks you've already decided moved to evaluate-…
Both fixed releases were scanned under the current scanner and policy, so finding, permission and dependency changes are available.
These older immutable releases were observed by prior successful syncs. They remain recorded when a newer release becomes current.
sha256:6f3f40bbcce76eebe972e97cc2f5fe2b441bc7bcdf4ec1a7852eb5a8fcd65f60