Skip to main content
Run any Skill in Manus
with one click
$pwd:
compozy
GitHub creator profile

compozy

Repository-level view of 111 collected skills across 9 GitHub repositories, including approximate occupation coverage.

skills collected
111
repositories
9
occupation fields
3
updated
2026-05-31
occupation focus
Major fields detected across this creator.
repository map

Where the skills live

Top repositories by collected skill count, with their share of this creator catalog and occupation spread.

Showing the top 8 repositories here; full repository list continues below.
repository explorer

Repositories and representative skills

#001
agh
54 skills1276updated 2026-05-31
49% of creator
agh
Software Developers

AGH runtime and contribution guide. Use for sessions, agents, native tools, skills, memory, network, tasks, capabilities, bundles, QA, docs, and repo work. Do not use for unrelated projects.

2026-05-31
autoreview
unclassified

Auto Review closeout. Codex review is the default when no engine is set and is the recommended reviewer.

2026-05-27
cy-codex-loop
Software Developers

Drives end-to-end execution of a Compozy techspec across many agent restarts by detecting the current phase from state.yaml plus .compozy/tasks/<slug>/, then activating the correct cy-* skill chain or the Compozy -> Claude Opus delegation lane for one iteration before stopping. Each Phase B iteration ends with an atomic checkpoint commit so every completed task or slice becomes a restorable git snapshot. Use when running a Compozy techspec under the codex-loop-plugin in goal mode, or when manually iterating through tasks, qa-report, and qa-execution with persistent memory and state. Do not use for one-off tasks without a .compozy/tasks/<slug>/ directory, for techspec authoring (use cy-create-techspec), or for any work that does not require iteration tracking across agent restarts.

2026-05-22
cy-impl-peer-review
Software Developers

Runs an optional cross-LLM peer review of an implemented change via compozy exec --ide claude --model opus --reasoning-effort xhigh and requires the reviewer to write a scoped Markdown findings artifact for user-directed remediation. Use after any implementation pass (feature, bug fix, refactor) when the user explicitly asks for an external Opus review of the diff before commit or PR. Do not use for TechSpec review (use cy-spec-peer-review), automatic remediation, batched provider review fetching (use cy-fix-reviews), manual self-review without an external LLM (use cy-review-round), or auto-looped review cycles.

2026-05-22
cy-spec-peer-review
Software Developers

Runs an optional cross-LLM peer review of a TechSpec via compozy exec --ide claude --model opus --reasoning-effort xhigh and requires the reviewer to write a scoped Markdown findings artifact for user-directed incorporation. Use when a TechSpec draft has already been approved by the user and they want an external review round, especially for autonomy/network/memory-impacting designs. Do not use for PRDs, automatic approval gates, code review batches, or auto-looped review cycles.

2026-05-22
qa-execution
Software Quality Assurance Analysts & Testers

Executes real-user QA sessions through public interfaces using personas, journeys, exploratory charters, test tours, edge-case probes, CFR checks, and browser evidence. Reads qa-report artifacts from <qa-output-path>/qa/ when present, captures issues/screenshots/reports under the same output tree, and classifies bugs by user impact. Use when validating a release candidate, migration, refactor, or user-facing change against production-like behavior. Do not use for AI implementation audits, task-status reconciliation, CI gate runs, integration/security/performance templates, or flaky-test triage; use agent-output-audit for those.

2026-05-14
agh-cleanup-failure-paths
Software Developers

Audits Go functions with multi-step setup or teardown for cleanup discipline on every error return: cancel any context created or extended, close every opened resource, release every claim or lease, stop every spawned subprocess, drain every HTTP body. Forbids http.DefaultClient in production code paths. Use when editing functions in internal/acp, internal/session, internal/scheduler, internal/coordinator, internal/extension, internal/automation, internal/store, internal/memory, internal/api, or any subprocess or registry handler. Do not use for read-only helpers, pure data structures, or tests.

2026-05-12
agh-code-guidelines
Software Developers

Enforces AGH Go code style and concurrency patterns before writing or editing any production Go file: error wrapping with %w, errors.Is/As only (no strings.Contains on err.Error), no underscore-discarded errors, slog over log/fmt, context.Context as first arg, compile-time interface assertions, no hardcoded config, CLI flag presence detection, whitespace normalization at CLI boundary, no comments restating WHAT, goroutine ownership and shutdown via context, no fire-and-forget, no time.Sleep in orchestration. Use whenever creating or modifying any *.go file under cmd/ or internal/ that is not a test file. Do not use for *_test.go (use agh-test-conventions), schema migrations (use agh-schema-migration), or contract changes (use agh-contract-codegen-coship).

2026-05-12
Showing top 8 of 54 collected skills in this repository.
#002
compozy
32 skills2.2k112updated 2026-05-27
29% of creator
compozy
Software Developers

Explains Compozy capabilities, CLI commands, core workflow skills, optional extension skills, configuration, artifact structure, reusable agents, and extensions. Use when the user asks how to use Compozy, what commands are available, how the workflow pipeline works, or how to configure a workspace. Do not use for executing workflow steps — use the specific cy- skills instead.

2026-05-27
compozy
Software Developers

Explains Compozy capabilities, CLI commands, core workflow skills, optional extension skills, configuration, artifact structure, reusable agents, and extensions. Use when the user asks how to use Compozy, what commands are available, how the workflow pipeline works, or how to configure a workspace. Do not use for executing workflow steps — use the specific cy- skills instead.

2026-05-25
cy-impl-peer-review
Software Quality Assurance Analysts & Testers

Runs an optional cross-LLM peer review of an implemented change via compozy exec --ide claude --model opus --reasoning-effort xhigh and packages findings for user-directed remediation. Use after any implementation pass (feature, bug fix, refactor) when the user explicitly asks for an external Opus review of the diff before commit or PR. Do not use for TechSpec review (use cy-spec-peer-review), automatic remediation, batched provider review fetching (use cy-fix-reviews), manual self-review without an external LLM (use cy-review-round), or auto-looped review cycles.

2026-05-04
compozy
Software Developers

Explains Compozy capabilities, CLI commands, core workflow skills, optional extension skills, configuration, artifact structure, reusable agents, and extensions. Use when the user asks how to use Compozy, what commands are available, how the workflow pipeline works, or how to configure a workspace. Do not use for executing workflow steps — use the specific cy- skills instead.

2026-05-04
cy-create-prd
Project Management Specialists

Creates a Product Requirements Document through interactive brainstorming with parallel codebase and web research. Use when starting a new feature or product, building a PRD, or brainstorming requirements. Do not use for technical specifications, task breakdowns, or code implementation.

2026-05-04
cy-create-tasks
Project Management Specialists

Decomposes PRDs and TechSpecs into detailed, independently implementable task files with enrichment from codebase exploration. Use when a PRD or TechSpec exists and needs to be broken down into executable tasks, or when task files need enrichment with implementation context. Do not use for PRD creation, TechSpec generation, or direct task execution.

2026-05-04
cy-create-techspec
Software Developers

Creates a Technical Specification by translating PRD business requirements into implementation designs through interactive technical clarification. Use when a PRD exists and needs a technical plan, or when technical architecture decisions need documentation. Do not use for PRD creation, task breakdown, or direct code implementation.

2026-05-04
cy-final-verify
Software Quality Assurance Analysts & Testers

Enforces fresh verification evidence before any completion, fix, or passing claim, and before commits or PR creation. Use when an agent is about to report success, hand off work, or commit code. Do not use for early planning, brainstorming, or tasks that have not yet reached a concrete verification step.

2026-05-04
Showing top 8 of 32 collected skills in this repository.
#003
arky
9 skills00updated 2026-03-17
8.1% of creator
creating-spec
Management Analysts

Create comprehensive technical specs for SDK gaps, feature modules, or system centralization efforts. Use when writing specs, PRDs, gap analysis documents, or planning centralization of scattered functionality into a single module. Triggers on "create spec", "write spec", "gap spec", "centralize", "fill the gap".

2026-03-17
adversarial-review
Software Quality Assurance Analysts & Testers

Adversarial code review using the opposite model. Spawns 1–3 reviewers on the opposing model (Claude spawns Codex, Codex spawns Claude) to challenge work from distinct critical lenses. Triggers: "adversarial review".

2026-03-16
deep-research
Correspondence Clerks

Perform comprehensive research and analysis using multiple discovery and analysis tools to provide a solid foundation for complex tasks.

2026-03-16
find-rules
Project Management Specialists

Discover and understand project rules, coding standards, and architectural guidelines before starting a task. Use when you need to know the constraints, patterns, or compliance requirements for a feature, file, or technology.

2026-03-16
git-rebase
Software Developers

Intelligently handle git rebase operations and resolve merge conflicts while preserving features and maintaining code quality. Use when rebasing feature branches, resolving conflicts across commits, and ensuring clean linear history without losing changes.

2026-03-16
no-workarounds
Software Developers

Enforce root-cause fixes over workarounds, hacks, and symptom patches in all software engineering tasks. Use when debugging issues, fixing bugs, resolving test failures, planning solutions, making architectural decisions, or reviewing code changes. Activates gate functions that detect and reject common workaround patterns such as type assertions, lint suppressions, error swallowing, timing hacks, and monkey patches. Don't use for trivial formatting changes or documentation-only edits.

2026-03-16
rust-coding-guidelines
Software Developers

Use when asking about Rust code style or best practices. Keywords: naming, formatting, comment, clippy, rustfmt, lint, code style, best practice, P.NAM, G.FMT, code review, naming convention, variable naming, function naming, type naming, 命名规范, 代码风格, 格式化, 最佳实践, 代码审查, 怎么命名

2026-03-16
sourcebot
Software Developers

Search external libraries and frameworks using Sourcebot MCP. Use when researching external code patterns, library APIs, framework examples, or documentation from repositories like Effect-TS/effect, vercel/ai, tanstack/query. NEVER use for local project code.

2026-03-16
Showing top 8 of 9 collected skills in this repository.
#004
helpdesk_example
4 skills00updated 2026-04-07
3.6% of creator
cy-create-tasks
unclassified

Decomposes PRDs and TechSpecs into detailed, independently implementable task files with enrichment from codebase exploration. Use when a PRD or TechSpec exists and needs to be broken down into executable tasks, or when task files need enrichment with implementation context. Do not use for PRD creation, TechSpec generation, or direct task execution.

2026-04-07
cy-fix-reviews
Software Quality Assurance Analysts & Testers

Executes provider-agnostic PR review remediation using existing review round files under .compozy/tasks/<name>/reviews-NNN/. Use when resolving batched review issues, updating issue markdown files, implementing fixes, and verifying the result. Do not use for PRD task execution, review export/fetch, or generic coding tasks without review issue files.

2026-04-07
cy-idea-factory
unclassified

Expands a raw idea into a structured, research-backed spec in .compozy/tasks/<slug>/_idea.md through interactive brainstorming, web research, business analysis, and multi-advisor debate. Use when the user has a feature idea and wants to explore and structure it before creating a PRD. Do not use for PRD creation, technical specifications, task breakdown, or code implementation.

2026-04-07
cy-review-round
unclassified

Performs a comprehensive code review of a PRD implementation and generates a review round directory with issue files compatible with cy-fix-reviews. Use when reviewing implemented PRD tasks, creating a manual review round without an external provider, or performing a quality audit of code changes. Do not use for fetching reviews from external providers, fixing existing review issues, executing PRD tasks, or editing source code.

2026-04-07
#005
skeeper
3 skills706updated 2026-05-18
2.7% of creator
#006
cc-loop
3 skills10updated 2026-05-10
2.7% of creator
#007
kb
2 skills634updated 2026-05-19
1.8% of creator
#008
codex-loop
2 skills341updated 2026-05-12
1.8% of creator
#009
releasepr
2 skills20updated 2026-05-18
1.8% of creator
Showing 9 of 9 repositories
All repositories loaded