Skip to content

xonika9/agent-skills / skills/x9-onboarding

x9-onboarding

Verified

Use after installing or updating `x9-*` skills to check their readiness and compare the current harness with the bundled x9 configuration profile — «проверь готовность x9-скиллов», «настрой Codex как у автора», "check installed x9 skills", "apply the recommended harness settings". Do not use for general environment diagnosis, account authorization, or unrelated configuration editing.

references/opencode.md

View on GitHub
# OpenCode adapter

Use this adapter only from OpenCode. First inspect the current session's live skill,
agent, and tool catalogs. Their names, schemas, and availability are runtime facts; do
not derive them from files, remembered commands, or a package directory scan.

Check requirements under [Runtime Checks and Guidance](declarations.md#runtime-checks-and-guidance).

## Configuration

Use `profiles/opencode.json` with the single existing user file at
`~/.config/opencode/opencode.jsonc` or `~/.config/opencode/opencode.json`. Inspect the
current OpenCode V2 schema and live model, agent, MCP, and provider catalogs before
proposing profile paths. Never use `opencode debug config` or another command that emits
the merged configuration: provider and MCP credentials may be included in its output.

Add model-specific agents only when their exact provider, model, and effort variant are
available. The Exa MCP entry contains only an environment reference; applying it never
proves that the variable is set or that Exa is ready. State that `websearch.provider = "exa"` sends future search
queries to that external provider.

After approval, merge supported paths under the
[shared configuration contract](configuration.md), preserving JSONC comments and
unrelated entries. Validate through a JSONC-aware parser or a silent runtime validation
surface; do not validate with a command that prints resolved configuration or headers.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall