Skip to main content
Execute qualquer Skill no Manus
com um clique
Repositório GitHub

KeyStore

KeyStore contém 18 skills coletadas de heyallencao, com cobertura ocupacional por repositório e páginas de detalhe dentro do site.

skills coletadas
18
Stars
136
atualizado
2026-04-19
Forks
12
Cobertura ocupacional
3 categorias ocupacionais · 100% classificado
explorador de repositórios

Skills neste repositório

ks-brief
Especialistas em gestão de projetos

Lightweight task compressor. Turn messy input into a one-page brief that can route to roundtable or writing-plan without replacing direction decisions.

2026-04-19
ks-review
Analistas de garantia de qualidade de software e testadores

Formal quality gate with multi-persona review, confidence thresholds, and QA routing based on fresh verification evidence.

2026-04-19
ks-roundtable
Especialistas em gestão de projetos

Direction convergence skill. Use brainstorm, align, or challenge mode to turn messy questions or existing proposals into a clear directional decision.

2026-04-19
ks-writing-plan
Desenvolvedores de software

Use this when direction is already clear and the next job is to compress it into an executable block with scope, done criteria, and routing.

2026-04-19
ks-bug-triage
Desenvolvedores de software

Fast failure classifier. Decide whether the problem is a spec gap, an implementation bug, or a rollback candidate before routing to writing-plan, diagnose, or ship.

2026-04-19
ks-diagnose
Desenvolvedores de software

Use this when the system is broken, tests are failing, or behavior is abnormal and the root cause is still unknown. No investigation, no fix.

2026-04-19
ks-implement
Desenvolvedores de software

Use this when the current block is already clear and the job is to complete it. Default route comes from test-first; only controlled low-risk exceptions may enter directly.

2026-04-19
ks-test-first
Analistas de garantia de qualidade de software e testadores

Default behavior-locking stage for the current block. Write failing checks first, then implement. Only controlled low-risk exceptions may skip it.

2026-04-19
ks-verify
Analistas de garantia de qualidade de software e testadores

Use this when tests or runtime checks must be run to confirm a claim with fresh evidence before formal review.

2026-04-19
ks-pr-prep
Desenvolvedores de software

Delivery-context organizer. Compress post-review changes into reviewer-ready PR and merge context without replacing release decisions.

2026-04-19
ks-qa
Analistas de garantia de qualidade de software e testadores

Conditional real-runtime QA. Enter only when review set qa_required=true. Use Playwright by default, and degrade to manual validation when automation is unavailable.

2026-04-19
ks-release
Desenvolvedores de software

Use this after ship completes to decide what can be released, what must be disclosed, and what risks or skipped validation must be stated honestly.

2026-04-19
ks-ship
Desenvolvedores de software

Delivery closeout before release. Accepts review-approved changes, runs the final checks, generates execution guidance, and performs merge/deploy/canary only when the project is explicitly adapted for it.

2026-04-19
ks-handoff
Desenvolvedores de software

Cross-session handoff skill. Use it when the user explicitly wants to pause, switch sessions, resume prior work, restore a handoff package, or list recent handoffs.

2026-04-19
ks-orchestrate
Desenvolvedores de software

Global routing hub. Determine the correct entry mode, choose the next skill, and manage workflow state. Route session-transfer requests to handoff.

2026-04-19
ks-docs-writer
Desenvolvedores de software

Fact-based documentation writer. Compress completed implementation, verification, or release results into stable docs such as changelogs, ADRs, and migration notes.

2026-04-19
ks-help
Desenvolvedores de software

Keystone first-run entry. Use it for onboarding, scenario triage, and choosing the next skill without replacing orchestrate.

2026-04-19
ks-knowledge
Desenvolvedores de software

Lightweight knowledge compounding system. Retrieve first, write only when it is worth it, and prefer updating existing knowledge over creating more noise.

2026-04-19