Claude Statusbar
leeguooooo/claude-code-usage-bar
Manage cs (claude-statusbar) — switch theme/style/density, override severity colors, preview combinations, run doctor, reset config, install, upgrade (cs upgrade — the only supported upgrade path)…
Pattern GSD (Get Shit Done) - découper en tâches atomiques avec contextes subagent frais pour combattre le context rot.
Install Atomic Tasks
$ npx skills add TheBeardedBearSAS/claude-craft --skill atomic-tasks -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install TheBeardedBearSAS/claude-craft atomic-tasks --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/TheBeardedBearSAS/claude-craft.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/atomic-tasks .claude/skills/atomic-tasks && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "atomic-tasks" agent skill from https://github.com/TheBeardedBearSAS/claude-craft/tree/main/.claude/skills/atomic-tasks into .claude/skills/atomic-tasks/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "atomic-tasks", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/TheBeardedBearSAS/claude-craft/tree/main/.claude/skills/atomic-tasksType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add TheBeardedBearSAS/claude-craft --skill atomic-tasks -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install TheBeardedBearSAS/claude-craft atomic-tasks --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/TheBeardedBearSAS/claude-craft.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/atomic-tasks .agents/skills/atomic-tasks && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "atomic-tasks" agent skill from https://github.com/TheBeardedBearSAS/claude-craft/tree/main/.claude/skills/atomic-tasks into .agents/skills/atomic-tasks/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "atomic-tasks", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add TheBeardedBearSAS/claude-craft --skill atomic-tasks -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install TheBeardedBearSAS/claude-craft atomic-tasks --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/TheBeardedBearSAS/claude-craft.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/atomic-tasks .cursor/skills/atomic-tasks && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "atomic-tasks" agent skill from https://github.com/TheBeardedBearSAS/claude-craft/tree/main/.claude/skills/atomic-tasks into .cursor/skills/atomic-tasks/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "atomic-tasks", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/TheBeardedBearSAS/claude-craft.git --path .claude/skills/atomic-tasks--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add TheBeardedBearSAS/claude-craft --skill atomic-tasks -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install TheBeardedBearSAS/claude-craft atomic-tasks --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/TheBeardedBearSAS/claude-craft.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/atomic-tasks .gemini/skills/atomic-tasks && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "atomic-tasks" agent skill from https://github.com/TheBeardedBearSAS/claude-craft/tree/main/.claude/skills/atomic-tasks into .gemini/skills/atomic-tasks/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "atomic-tasks", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install TheBeardedBearSAS/claude-craft atomic-tasksInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add TheBeardedBearSAS/claude-craft --skill atomic-tasks -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/TheBeardedBearSAS/claude-craft.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/atomic-tasks .github/skills/atomic-tasks && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "atomic-tasks" agent skill from https://github.com/TheBeardedBearSAS/claude-craft/tree/main/.claude/skills/atomic-tasks into .github/skills/atomic-tasks/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "atomic-tasks", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add TheBeardedBearSAS/claude-craft --skill atomic-tasks -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install TheBeardedBearSAS/claude-craft atomic-tasks --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/TheBeardedBearSAS/claude-craft.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/atomic-tasks .opencode/skills/atomic-tasks && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "atomic-tasks" agent skill from https://github.com/TheBeardedBearSAS/claude-craft/tree/main/.claude/skills/atomic-tasks into .opencode/skills/atomic-tasks/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "atomic-tasks", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
atomic-tasks- GitHub stars
- 107
- Token cost
- ~1.1k tokens
- SKILL.md length
- 427 words
- Files
- 1
- Skills in repo
- 12
- Repo updated
- First seen
- Licence
- MIT
At a glance
Pattern GSD (Get Shit Done) - découper en tâches atomiques avec contextes subagent frais pour combattre le context rot.
- Works in 5 steps: Split work — Découper → Small plans — Plans courts par tâche → Fresh subagent contexts — Contexte neuf… → …
- Planning complex work
- SKILL.md covers Les 5 étapes du pattern GSD, Signaux qu'il faut appliquer…, Anti-patterns à éviter and Intégration Claude Craft, plus 1 more section
- Calls git
What it does
Atomic Tasks is an agent skill from TheBeardedBearSAS/claude-craft. Pattern GSD (Get Shit Done) - découper en tâches atomiques avec contextes subagent frais pour combattre le context rot. Use when planning complex work or working past 50% context usage.
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Agent Workflows, covering Subagents and Context engineering. The repository describes itself as: Supercharge Claude Code with Expert Knowledge A comprehensive framework for AI-assisted development. Install standardized rules, agents, and commands for your projects across… The licence is MIT.
When your agent uses it
- Planning complex work
- Working past 50% context usage
Example prompts
- “/atomic-tasks”
Workflow steps
5 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 99c1ee3. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
git
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
github.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Atomic Tasks loads about 1.1k tokens when it runs. Until then it costs about 50 tokens; SKILL.md has 427 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from TheBeardedBearSAS/claude-craft at commit 99c1ee3, republished under its MIT licence (© TheBeardedBearSAS). 427 words, ~1,093 tokens.
Download SKILL.mdSave it as
.claude/skills/atomic-tasks/SKILL.md (or your agent's skills folder).- name
- atomic-tasks
- description
- Pattern GSD (Get Shit Done) - découper en tâches atomiques avec contextes subagent frais pour combattre le context rot. Use when planning complex work or working past 50% context usage.
- context
- fork
Atomic Tasks — Pattern GSD (Get Shit Done)
Pattern inspiré de gsd-build/get-shit-done (Lex Christopherson, adopté par Amazon/Google/Shopify/Webflow).
Objectif : combattre le context rot (dégradation de la qualité au-delà de ~50% de contexte utilisé) en découpant le travail en tâches atomiques exécutées dans des subagents à contexte frais.
Les 5 étapes du pattern GSD
1. Split work — Découper
Découper la feature en tâches atomiques :
- Chacune exprimable en 1-3 phrases
- Chacune réalisable en < 30 minutes
- Chacune testable indépendamment
- Chacune committable en un commit atomique
❌ MAUVAIS : "Ajouter le système d'authentification"
✅ BON :
1. "Créer la table users avec migration"
2. "Implémenter POST /auth/register avec validation email"
3. "Implémenter POST /auth/login retournant JWT"
4. "Ajouter middleware JWT verification"
5. "Tests d'intégration du flow login"2. Small plans — Plans courts par tâche
Pour chaque tâche atomique, un plan court :
- 1 objectif
- 3-5 étapes max
- Critères de succès explicites (test qui passe, endpoint qui répond, fichier qui existe)
3. Fresh subagent contexts — Contexte neuf à chaque tâche
Règle fondamentale : chaque tâche atomique s'exécute dans un subagent à contexte frais (via Task tool ou /clear entre tâches).
| Raison | Impact |
|---|---|
| Contexte < 30% au démarrage | Qualité réponses maximale |
| Pas de résidus de la tâche précédente | Zéro confusion cross-task |
| Coût tokens optimisé | Pas de relecture inutile du contexte accumulé |
| Parallélisable | Plusieurs subagents en simultané |
Implémentation :
- Utiliser
Agenttool avecsubagent_type=general-purposeou spécialisé - Passer UNIQUEMENT le contexte nécessaire (pas tout le projet)
- Demander un rapport concis à la fin (< 200 mots)
4. Atomic git commits — Commits atomiques
Chaque tâche = 1 commit. Jamais de commit qui mélange 2 tâches.
✅ BON :
commit 1 : "feat(auth): add users table migration"
commit 2 : "feat(auth): implement register endpoint"
commit 3 : "feat(auth): implement login endpoint"
❌ MAUVAIS :
commit 1 : "feat: auth system + bug fixes + refactor"Bénéfice : git bisect efficace, reverts ciblés, review facilitée.
5. Verify goals — Vérifier chaque objectif
Avant de passer à la tâche suivante, vérifier explicitement que l'objectif est atteint :
- Le test écrit passe
- L'endpoint répond avec le bon code HTTP
- Le build compile
- Le linter passe
- Le comportement utilisateur est observable
Règle : pas de "je pense que ça marche". Preuve ou pas fini.
Show full SKILL.md (149 more words)Show less
Signaux qu'il faut appliquer ce pattern
- Contexte utilisé > 50%
- Tâche qui s'étale sur > 1h sans livrable intermédiaire
- Réponses de Claude qui deviennent moins précises
- Besoin de re-expliquer des choses déjà dites
- Multiple responsabilités dans une seule demande
Anti-patterns à éviter
| Anti-pattern | Pourquoi mauvais |
|---|---|
| Kitchen-sink session | Tout faire dans 1 session = context rot garanti |
| Tâche non testable | Impossible à vérifier = jamais "done" |
| Commit mélangé | Review impossible, revert dangereux |
| Pas de clear entre tâches | Pollution inter-tâches |
| Planification excessive | 10 étapes pour changer 1 ligne = overhead |
Intégration Claude Craft
/workflow:analyze— phase d'analyse BMAD doit produire des tâches atomiques/common:ralph-run— Ralph doit itérer sur des tâches atomiques, une par boucle- Agent tool — chaque tâche complexe déléguée à un subagent frais
- Rule 12 (context-management) —
/clearobligatoire entre tâches non liées - Rule 23 (karpathy-principles) — minimal code par tâche
Ressources
- gsd-build/get-shit-done
- Rule
.claude/rules/01-workflow-analysis.md - Rule
.claude/rules/12-context-management.md - Command
/common:sub-agents-patterns
Date de dernière mise à jour : 2026-04-15 Version : 1.0.0
© TheBeardedBearSAS, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .claude/skills/atomic-tasks of TheBeardedBearSAS/claude-craft.
Open the folder on GitHubat commit 99c1ee3
Compare with similar skills
Atomic Tasks next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Atomic Tasks this skillTheBeardedBearSAS/claude-craft | 107 | — | ~1.1k | Automated safety check: Pass | MIT | |
| Claude Statusbarleeguooooo/claude-code-usage-bar | 377 | — | ~2.5k | Automated safety check: Pass | MIT | |
| Badstephenleo/bmad-autonomous-development | 107 | — | ~7.7k | Automated safety check: Pass | MIT | |
| Analyze Trajectoryyologdev/yoyo-evolve | 1.9k | — | ~3.6k | Automated safety check: Pass | MIT | |
| Code Context Slicingtrailofbits/skills | 7.4k | — | ~2.1k | Automated safety check: Pass | CC-BY-SA-4.0 | |
| MoAI Foundation Coremodu-ai/moai-adk | 1.2k | — | ~5k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Bad
stephenleo/bmad-autonomous-development
BMad Autonomous Development — orchestrates parallel story implementation pipelines.
Analyze Trajectory
yologdev/yoyo-evolve
Diagnoses a recurring failure such as a stuck task, repeated CI error or frequent reverts by sending sub-agents through the logs and returning one root-cause diagnosis.
- Official
Code Context Slicing
trailofbits/skills
Picks a small, graph-based slice of source with Trailmark and hands a focused code task to a smaller or local model without exposing the whole repository.
MoAI Foundation Core
modu-ai/moai-adk
Reference for MoAI-ADK's core development principles: TRUST 5 quality gates, SPEC-first domain-driven workflow, agent delegation and token budgeting.
Cc Dev Agent
sangrokjung/claude-forge
A skill your agent uses when starting Claude Code projects, writing CLAUDE.md/spec.md, dispatching subagents, or requesting Agent Teams parallel development.
More from TheBeardedBearSAS/claude-craft
All 12 skills in this repoArchitect
TheBeardedBearSAS/claude-craft
Phase d'architecture systématique AVANT le code (TDD). An agent skill from TheBeardedBearSAS/claude-craft.
Async
TheBeardedBearSAS/claude-craft
Architecture async-first avec messaging et queues (Symfony Messenger, Laravel Queue, Ecotone).
Cqrs
TheBeardedBearSAS/claude-craft
CQRS - Command Query Responsibility Segregation. An agent skill from TheBeardedBearSAS/claude-craft.
Design Md Convention
TheBeardedBearSAS/claude-craft
Convention DESIGN.md pour design systems AI-friendly. An agent skill from TheBeardedBearSAS/claude-craft.
Docker Hadolint
TheBeardedBearSAS/claude-craft
Docker & Hadolint validation (2026). An agent skill from TheBeardedBearSAS/claude-craft.
Dynamic Workflows
TheBeardedBearSAS/claude-craft
Orchestrate dozens-to-hundreds of subagents from a script Claude writes (Claude Code Dynamic Workflows, trigger ultracode).
Related
Categories
Questions about Atomic Tasks
What does Atomic Tasks do?
Pattern GSD (Get Shit Done) - découper en tâches atomiques avec contextes subagent frais pour combattre le context rot. Atomic Tasks is an agent skill from TheBeardedBearSAS/claude-craft. Pattern GSD (Get Shit Done) - découper en tâches atomiques avec contextes subagent frais pour combattre le context rot.
When should I use Atomic Tasks?
Atomic Tasks fits situations like: planning complex work; working past 50% context usage.
How do I install Atomic Tasks in Claude Code?
Run `npx skills add TheBeardedBearSAS/claude-craft --skill atomic-tasks -a claude-code`. Or copy the skill folder (.claude/skills/atomic-tasks in TheBeardedBearSAS/claude-craft) into .claude/skills/atomic-tasks in your project. Claude Code loads it when a task matches its description.
How do I install Atomic Tasks in Codex?
Run `npx skills add TheBeardedBearSAS/claude-craft --skill atomic-tasks -a codex`. Or copy the skill folder (.claude/skills/atomic-tasks in TheBeardedBearSAS/claude-craft) into .agents/skills/atomic-tasks in your project. Codex loads it when a task matches its description.
Can I use Atomic Tasks in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add TheBeardedBearSAS/claude-craft --skill atomic-tasks -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/atomic-tasks, .gemini/skills/atomic-tasks, .github/skills/atomic-tasks and .opencode/skills/atomic-tasks in your project.
What does Atomic Tasks need to run?
Going by SKILL.md and its folder, Atomic Tasks needs the command-line tools its instructions call (git).
Does Atomic Tasks access the network?
SKILL.md names 1 domain. As links in the text: github.com. This is read from the text; nothing was executed.
Is Atomic Tasks safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Atomic Tasks use?
Atomic Tasks is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Atomic Tasks use?
About 1.1k tokens (SKILL.md is roughly 4.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Atomic Tasks?
Skills that share tags, products or a category with Atomic Tasks: Claude Statusbar (leeguooooo/claude-code-usage-bar, 377 stars), Bad (stephenleo/bmad-autonomous-development, 107 stars), Analyze Trajectory (yologdev/yoyo-evolve, 1.9k stars) and Code Context Slicing (trailofbits/skills, 7.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Atomic Tasks?
TheBeardedBearSAS (a GitHub organization) maintains it in TheBeardedBearSAS/claude-craft, which has 107 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on September 14, 2026.
Source: TheBeardedBearSAS/claude-craft on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.