Skip to content

MVPavan/via / .claude/skills/authoring-for-agents

authoring-for-agents

Verified

Use when creating or changing agent instructions or their activation behavior. Skip edits that only correct spelling or formatting.

FileKindSize
SKILL.mdskill md2.4 KB
agents/openai.yamlconfig42 B
references/skill-anatomy.mdmarkdown1.8 KB
references/testing-docs.mdmarkdown1.4 KB
references/writing-principles.mdmarkdown1.8 KB

references/skill-anatomy.md

View on GitHub
# Skill packaging

Keep one canonical directory per workflow with `SKILL.md`; add references only
for substantial conditional material and scripts for reusable mechanical work.
Inline the common contract. Avoid mandatory chains of references.

## Frontmatter and invocation

Require `name` matching the directory and a concise `description` naming the
activation boundary. Put important exclusions near the positive trigger. A short
outcome phrase is acceptable when it improves selection; do not duplicate the
whole workflow or assume any wording technique guarantees invocation behavior.

Use `disable-model-invocation: true` for manual workflows and compatibility
aliases. The paired Codex policy is `agents/openai.yaml` →
`policy.allow_implicit_invocation: false`. This repository's catalog generator
updates that sidecar and the router together. Actual catalog exposure and context
loading depend on the harness; inspect discovery instead of assuming zero cost.

A manual entrypoint can delegate to a shared workflow when explicitly requested.
Keep its body thin and preserve the user's authority boundaries. Other skills
should select the canonical owner rather than automatically activating aliases.

## Cross-references and verification

Name the owner and the condition for reading a reference. Use relative links for
nearby skill material and repository paths for project policy. Keep model IDs,
reasoning controls and tool-interface differences in runtime integration.

After metadata or routing edits, regenerate the catalog/sidecars and run the
catalog check. Check caller references and existing integration links before
removing an entrypoint. Compatibility pointers are appropriate when an authorized
edit scope excludes those integration files. Structural validity does not prove
behavioral routing; test representative positive and negative tasks when feasible.
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: 472kUpdated 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