claude-allow-stop
Return to normal stop behavior. Use PROACTIVELY after completing all tasks in continuous work mode, when work is committed and tests pass, or when reaching natural stopping point. User can invoke with /claude-allow-stop.
npx skills add majiayu000/claude-skill-registry --skill claude-allow-stop-manuelkugelmann-bitbot-2 --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Disable Stop Hook Automation Allow normal completion and wait for user input. ```bash .claude/skills/claude-allow-stop/scripts/allow-stop.sh ``` Or user invokes: `/claude-allow-stop` Re-enable with `/claude-do-not-stop [reason]`
What does the claude-allow-stop skill do?
Return to normal stop behavior. Use PROACTIVELY after completing all tasks in continuous work mode, when work is committed and tests pass, or when reaching natural stopping point. User can invoke with /claude-allow-stop.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill claude-allow-stop-manuelkugelmann-bitbot-2 --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.