context-manager
Skill28 starsChanged 3 months agoApache-2.0View on GitHub
Organiza contexto, tarefas e handoff entre sessoes. Trigger em: "criar tarefa", "lista de tarefas", "status", "progresso", "trocar foco", "resetar contexto", "o que falta", "proxima tarefa", "historico", "pipeline de tarefas".
14 other projects use a version of this.
Adopted by
Most recently taken up by
- AtilaMedeiros/skillstheir own version, first seen Nov 16, 2026
- tturupapa-stack/agent-company-v5.1their own version, first seen Nov 8, 2026
- shino369/claude-code-personal-workspacetheir own version, first seen Nov 8, 2026
- Mark393295827/graph-engineering-architecturestheir own version, first seen Nov 8, 2026
- davidanthonyn/claude-skillstheir own version, first seen Oct 20, 2026
- xfstudio/skillstheir own version, first seen Oct 13, 2026
Other versions14 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 14
- gaoziman/claude-context-manager★ 87same name
- jshsakura/awesome-opencode-skills★ 31same name
- belokonm/claude-supercode-skills★ 11same name
- valsecchi75/project-scaffolder★ 9same name
- xfstudio/skills★ 9same name
- nicolasestrem/antigravity-gemini-skills★ 8same name
- Mark393295827/graph-engineering-architectures★ 4same name
- shino369/claude-code-personal-workspace★ 4same name
- ai4brands-design/claude-skills★ 2same name
- AtilaMedeiros/skills★ 1same name
4 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository92 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- po-feature-specSkill
- ui-ux-designSkill
- backend-apiSkill
- frontend-integrationSkill
- qa-testingSkill
- security-reviewSkill
- deploy-dockerSkill
- orchestratorSkill
- documenterSkill
- reviewerSkill
- motion-designSkill
- marketing-copySkill
- seo-specialistSkill
- mobile-tauriSkill
- image-generatorSkill
- repo-auditorSkill
- asset-librarianSkill
- observability-sreSkill
- data-analyticsSkill
- accessibility-specialistSkill
- migration-refactor-specialistSkill
- release-managerSkill
- ai-integration-architectSkill
- prompt-engineerSkill
- video-integration-specialistSkill
- claude-md-generatorSkill
- design-intelligenceSkill
- cost-trackerSkill
- session-summarySkill
- smart-suggestionsSkill
- detective-specSkill
- static-analysisSkill
- skill-authorSkill
- web-asset-generatorSkill
- tdd-engineerSkill
- architecture-deepenerSkill
- program-routerSkill
- parallel-dispatcherSkill
- blog-publisherSkill
- blog-screenshotSkill
- canary-deploymentSkill
- zoom-outSkill
- handoff-contextSkill
- post-deploy-canary-monitorSkill
- pattern-conformitySkill
- research-prepSkill
- context-budgetSkill
- direct-response-copySkill
- ux-researchSkill
- ui-polishSkill
- doubt-driven-reviewSkill
- video-analysisSkill
- marketing-reporting-analyticsSkill
- responsive-conversionSkill
- mobile-ux-foundationsSkill
- i18n-localizationSkill
- closed-loop-revenueSkill
- app-reference-architectureSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 11 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 71
no maximo 15 tarefas ativas antes de priorizar ou arquivar
“Common” is measured: kept by at least 6 in 10 of the 11 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Context Manager - Gerenciamento de Contexto e Tarefas
O Context Manager mantem foco, rastreabilidade e continuidade sem inflar contexto.
Governanca Global
Esta skill herda comportamento base de GLOBAL.md e destas policies:
policies/execution.mdpolicies/persistence.mdpolicies/token-efficiency.mdpolicies/handoffs.mdpolicies/evals.md
Se houver conflito entre instrucoes, a hierarquia global do kit prevalece.
Quando Usar
- criar ou reorganizar lista de tarefas
- registrar mudanca de foco, bloqueio ou decisao relevante
- resumir estado atual para continuidade entre sessoes
- manter dependencias entre frentes visiveis
Quando Nao Usar
- para substituir a logica do Orquestrador
- para persistir conversa operacional longa sem valor futuro
- para registrar detalhes triviais que nao ajudam a proxima etapa
Entradas Esperadas
- pedido atual do usuario
- plano ou pipeline em execucao
- estado atual das tarefas
- dependencias, bloqueios e decisoes relevantes
Saidas Esperadas
- lista de tarefas atualizada
- foco atual resumido
- historico enxuto quando houver troca de contexto
- handoff curto para o Orquestrador ou proxima skill
Responsabilidades
- Criar listas de tarefas a partir de specs, issues ou pedidos do usuario
- Atualizar status das tarefas em tempo real conforme progresso
- Detectar mudanca de foco quando o usuario muda de assunto
- Resumir e persistir apenas o que ajuda a proxima sessao
- Tornar dependencias e blockers visiveis
Ciclo de Vida de uma Tarefa
Usar o mecanismo disponivel no ambiente:
Criar item (pending) -> Atualizar para in_progress -> Execucao -> Atualizar para completed -> Revisar lista geral
Checkpoint antes de marcar completed: confirmar que a evidencia de conclusao (ver policies/verification-before-completion.md) existe de fato — nao marcar completo so porque a etapa foi tentada. Se a verificacao falhar, a tarefa volta pra in_progress com a razao anotada, nao pra pending (perderia o progresso) nem pra completed (mentiria pro proximo passo do pipeline).
Regras de Operacao
- titulo no imperativo e curto
- uma tarefa
in_progresspor vez quando possivel - no maximo 15 tarefas ativas antes de priorizar ou arquivar
- bloquear ruido e manter so o necessario para continuidade
Mudanca de Foco
Quando o pedido sair do escopo atual:
- identificar se o novo pedido compete com o trabalho ativo
- confirmar com o usuario apenas se arquivar puder ocultar algo ainda importante
- persistir resumo curto do contexto anterior
- registrar o novo foco com tarefas iniciais
Persistencia Recomendada
Preferencia de mecanismos:
- ferramenta nativa de task ou memoria do ambiente
- arquivo local sob
docs/context/quando o ambiente for stateful - resumo curto em handoff quando nao houver persistencia entre sessoes
Se usar arquivo local, preferir docs/context/current-focus.md e docs/context/history.md.
Integracao com Orchestrator
- o Orquestrador decide qual skill executa
- o Context Manager acompanha progresso, dependencias e blockers
- cada etapa concluida gera estado resumido e pronto para handoff
Evidencia de Conclusao
- lista de tasks coerente com o foco atual
- estado atual resumido sem ruido operacional
- dependencias e blockers visiveis para a proxima etapa
Skills Utilitárias (context: fork)
Quando uma sub-operação desta skill for puramente mecânica — ler cache, gravar estado, checar arquivo — sem necessidade de raciocínio do modelo, preferir o padrão:
# frontmatter da sub-skill utilitária
context: fork
disable-model-invocation: trueIsso isola a execução e evita consumir contexto do agente principal para tarefas
que são essencialmente I/O. Padrão observado em addozhang/mem9
(Apache-2.0) nas skills recall, store e setup.
Quando aplicar: sub-skills de leitura de vault, gravação de estado de sessão, verificação de auth, fetch de memória externa. Não aplicar quando a operação requer julgamento contextual (ex: decidir o que salvar, priorizar tasks).
Handoff
Seguir policies/handoffs.md e, quando util, templates/handoff.md.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

