Individual skill
oss-maintainer-workflow
Use when maintaining or releasing a public open-source repository, including issue triage, pull request review, dependency or security remediation, release preparation, and source-linked adoption reporting.
plugins/kevin592/codex-full-stack-workflow/skills/oss-maintainer-workflow/SKILL.md
Source commit d780783eba4ecc7c8b9429f95c9362df95f07c61
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 4, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 1,540
- Repository last updated
- Nov 7, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai-coding Repository topic
- awesome Repository topic
- awesome-list Repository topic
- codex Repository topic
- codex-plugins Repository topic
- openai Repository topic
- codex-skill Repository topic
- codex-skills Repository topic
- marketplace Repository topic
- codex-marketplace Repository topic
- operations Derived category
- security Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 3,689 bytesSKILL.mdcore · 3,689 bytesreferences/maintenance-evidence-contract.mddoc · 1,900 bytes
Read excerpt
# OSS Maintainer Workflow
Run one small, verifiable maintenance cycle for a public repository. The goal is
not activity volume. The goal is a real maintainer outcome backed by public
issues, pull requests, CI, security checks, release notes, and honest adoption
evidence.
## Input Artifacts
- Public repository URL and license
- Current issue and pull request queue
- Latest release and changelog
- CI and dependency/security status
- Real user feedback, external listings, or downstream references when they exist