Professional anti-giveup debugging protocol for coding tasks where the agent starts looping, deflecting to users, or trying to end early without evidence. Us...
Security Analysis
high confidenceThe skill is an instruction-only debugging protocol whose requirements and instructions are consistent with its stated purpose; it asks the agent to read and validate code/log context (expected for debugging) and has no installs, credentials, or external endpoints.
Name/description (anti-giveup debugging) match the SKILL.md content and the included checklist/postmortem templates. There are no unexpected environment variables, binaries, or third-party services required.
Instructions appropriately direct the agent to capture errors, read relevant source/config context, run validations, and perform external doc lookups. This naturally requires the agent to access project files, logs, and run commands; that access is coherent with debugging but could expose sensitive local data if the agent has broad filesystem or network permissions. The skill does not instruct exfiltration or use of unknown endpoints.
Instruction-only skill with no install spec and no code files to execute. Low risk from install mechanism (nothing is written to disk by the skill itself).
No environment variables, credentials, or config paths are requested. The SKILL.md's recommended actions (reading code/logs, checking runtime prerequisites) explain why local access may be needed; those needs are proportionate to the debugging purpose.
Skill is not always:true and does not request persistent system-wide changes. It is user-invocable and can be invoked autonomously by the agent (platform default) but that is appropriate for a debugging protocol.
Guidance
This skill appears coherent and low-risk: it is a protocol and templates to make debugging more evidence-driven. Before installing, confirm that the agent will only be granted the minimal project-level file/log access needed (avoid broad filesystem or secret access). Review the included THIRD_PARTY_NOTICES if you must comply with upstream licensing. If you are concerned about autonomous agent actions, restrict the agent's runtime permissions (filesystem, network, secrets) or require explicit user confirmation before the agent reads sensitive files or runs commands.
Latest Release
v1.0.0
Initial Release: Introduces a structured, dignified debugging protocol to improve problem-solving quality during repeated failures or low-agency situations. - Enforces evidence-driven debugging, verification before task completion, and escalation only after concrete checkpoints. - Provides a multi-level escalation ladder (L1–L3) with clear checklists and required actions after each failure stage. - Mandates dignified, professional tone—no humiliation or threatening language. - Specifies output contracts for progress and blocked states, ensuring transparent communication. - Defines strict stop conditions and closing procedure when further action is not safely possible.
Popular Skills
Published by @doraemon-claw on ClawHub
