contribute

Drafts and applies source-level changes to shared capability packages with scoped contribution workflows.

3|1|Updated Jul 17, 2026
One-click install
npx skills add https://github.com/AlmogBaku/aos --skill contribute-almogbaku
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: contribute
Source: https://github.com/AlmogBaku/aos/tree/main/capabilities/capability-lifecycle/skills/contribute
Command: npx skills add https://github.com/AlmogBaku/aos --skill contribute-almogbaku

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? When a fix or improvement should benefit every user of a shared capability package rather than just one person's install, this Skill routes the change to the capability's shipped source instead of a personal overlay, and governs how that change reaches upstream safely. ## Core Features & Use Cases - Change classification: Distinguishes small tweaks (wording, thresholds, knob promotions) from major changes (new skills, schema or ownership changes) and applies the matching level of ceremony. - Promotion handling: Converts a personal MOD statement into a generic upstream mechanism — a {{mod: <key>}} slot, an ONBOARDING question, and a MOD.example placeholder — without leaking personal context. - Upstream contribution mechanics: Drafts signal issues and PRs with ledger searches, self-containment scrubs, lint gates, and dogfooding, never pushing, forking, or opening PRs without explicit user approval. - Use Case: A user notices the steward capability double-counts a slip for everyone. The Skill classifies it as small, drafts the fix on a branch in the upstream clone, runs the lint gate, and offers a PR body — sending nothing until the user says yes. ## Quick Start Ask your agent to promote a personal tweak or fix a bug in a shared capability, for example: "The steward should also flag missed follow-ups — make that a fix for all users."

Frequently Asked Questions about contribute

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I contribute a fix to an upstream capability package?▼

Classify the change as small or major first. Small fixes to upstream-shipped packages are drafted on a branch in the upstream clone and offered as a contribution; major changes re-run a scaled research, design, and approval procedure before anything is drafted.

How do I promote a personal MOD statement to a shared capability?▼

Extract the generic mechanism, never the literal personal text. The promotion adds a mod slot at the target site, a matching ONBOARDING question, and a MOD.example placeholder, with a ledger search deciding whether a signal issue or PR is warranted.

What is the difference between capability-evolve and capability-contribute?▼

Capability-evolve personalizes one user's install through the overlay, while contribute edits the capability's shipped source for everyone. Changes to upstream-shipped packages are drafted as contributions, never silently edited locally.

Can the agent open a PR or issue on GitHub automatically?▼

No. The Skill drafts PR bodies, issues, and branches but never pushes, forks, opens PRs, or files issues without the user's explicit approval. Every write that leaves the machine toward upstream requires an explicit yes.

When is a change classified as major instead of small?▼

A change is major when it creates, deletes, or rescopes anything: new skills, agents, schedules, schema or contract changes, or shifts in what the capability owns. Wording tweaks, thresholds, and knob promotions stay small.