Use source and execution tools to investigate a supplied program and check a proposed change against evidence.
74%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./agentpilot/src/agentpilot/policy/proposer/skills/proposer-guide/SKILL.mdRead missing code before relying on a name, diagram or docstring. Follow related_implementations into callees when a claim depends on their behavior.
Use paths and record references from the supplied directories:
Inspect relevant attempts before connecting their observations. Successful repeats help compare behavior, but neither success nor failure proves a cause. Executor explanations and printed self-verdicts are claims. A recorded tool result may mix terminal output and harness feedback; keep an unknown origin unknown. Keep early ideas provisional: check whether the change already exists, would trigger, or would still accept the recorded failure. Check whether its new action would occur in time to affect that failure. When counterevidence rules out the idea, revise the mechanism or narrow its applicability.
Independent reads may share a response; wait for results when the next action depends on them.
HKUDS/OpenSpace
e5a81e7
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.