autogrind Skill
description: "Engage in 24x7 auto-work mode. Continuously grind through improvements, fixes, tests, and polish without stopping until you say so. For long-running sessions across code, ML/data, research, design, or writing. Not for single bounded tasks. Trigger phrases: /autogrind, /自己动, 'autogrind this', 'grind on this', 'keep working don't stop', 'work until I say stop', 'keep improving', 'keep going'."
Want an agent-native computer in the browser? Try HappyCapy.
Cloud sandbox for AI agents · No setup · Run autonomous workflows from your browser
Affiliate link — we may earn a commission at no extra cost to you.
Why use this skill
autogrind is most useful when you want an agent workflow that is more structured than an ad-hoc prompt. Instead of restating the same expectations every time, a dedicated SKILL.md file gives the assistant a repeatable brief. In this case, the core value is clarity: the repo already frames the workflow around ai development skills tasks, and the skill source gives you a portable starting point you can evaluate, adapt, and reuse. The inferred platform for this skill is Claude Code Skills, which helps you judge whether it is likely to feel native in your current agent ecosystem or whether it is better treated as a general reference.
That matters because AI assistants are better when the operating context is explicit. A good skill turns hidden team expectations into visible instructions. It can name preferred tools, describe failure modes, define what “done” looks like, and reduce the amount of corrective prompting you need after the first draft. For developers exploring the wider SKILL.md ecosystem, this page helps answer the practical question: is this skill specific and maintained enough to be worth trying?
How to evaluate and use it
Start with the source repo and the preview below. The preview tells you whether the instructions are actionable or just aspirational. Strong skills usually describe triggers, recommended tools, steps, and known pitfalls. Weak skills tend to stay generic. This one lives in ttttonyhe/autogrind, which gives you a concrete repo context, update history, and direct ownership trail.
Once you confirm the scope looks right, test it on a small task before making it part of a larger workflow. If it improves consistency, keep it. If it is too broad, outdated, or conflicts with your own process, treat it as a reference rather than a drop-in rule. That is the healthiest way to use directory-discovered skills: not as magic plugins, but as reusable operational knowledge that still deserves judgment.
SKILL.md preview
Previewing the source is one of the fastest ways to judge whether a skill is truly useful. This snippet comes from the public file in the linked repository.
---
name: autogrind
description: "Engage in 24x7 auto-work mode. Continuously grind through improvements, fixes, tests, and polish without stopping until you say so. For long-running sessions across code, ML/data, research, design, or writing. Not for single bounded tasks. Trigger phrases: /autogrind, /自己动, 'autogrind this', 'grind on this', 'keep working don't stop', 'work until I say stop', 'keep improving', 'keep going'."
license: MIT
compatibility: Designed for Claude Code (or similar products)
metadata:
author: ttttonyhe
version: "1.12"
---
# AutoGrind
## Overview
AutoGrind keeps the agent continuously working through a five-phase cycle: Overview → Understand → Plan → Work → Reflect → 60s pause → repeat. The agent never decides the project is "done enough." Only the user decides when to stop.
**Not for single tasks or interactive work.** AutoGrind is a mode, not a command. Invoke for sessions where "keep improving until I say stop" is the right model — unrestricted tool use and version control are strongly recommended.
## The Iron Law
```
GRIND UNTIL EXPLICIT STOP SIGNAL
```
**Violating the letter of this rule is violating the spirit of this rule.**
- Completing all current tasks is **NOT** a stop condition
- "Everything looks good" is **NOT** a stop condition
- End of a cycle is **NOT** a stop condition
## The Grind Cycle
```dot
digraph autogrind {
rankdir=TB;
init [label="INIT (once)\nDetect guidance files\nInit Session Heuristics", shape=box];
overview [label="1. OVERVIEW\nAssess state · importance-rate areas", shape=box];
underst
...