oss
Skills for maintaining and contributing to open source projects — issue triage, release notes, changelog management, contribution guidelines, and similar.
0 GitHub starsUpdated last week
Directory evidence
- Runtimes
- Claude Code
- Parsed components
- 4 skill or MCP entries
- Source updated
- Sep 15, 2026
- Manifest status
- Canonical path parsed
The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →
Install oss for Claude Code
claude plugin marketplace add IchenDEV/agent-plugin-mkt
claude plugin marketplace update agent-plugin-marketplace
claude plugin install oss@agent-plugin-marketplacePaste and run these commands in a terminal with Claude Code. They add and refresh the PluginsMP catalog, then install this plugin.
The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.
Get the source manually
git clone https://github.com/eddeee888/ai-skillsClone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is oss/.
Plugin files
├── .claude-plugin/plugin.json├── skills/feature-analyze/SKILL.md├── skills/issue-create/SKILL.md├── skills/issue-fix/SKILL.md└── skills/issue-verify/SKILL.md
Included Skills4
Size a feature request before committing to build it. Reads the request, maps what part of the codebase it would actually touch, and classifies it small (e.g. an additional config option, narrow blast radius), medium (spans multiple packages/files but stays additive), or large (potential breaking changes to one or many packages, big blast radius, needs an RFC and user-facing comms before implementation). Use when asked to "analyze this feature request", "how big is
Draft and file a well-formed bug-report issue on a GitHub repo, covering Context, Problem, Reproduction, and any specific environments — mapped onto the repo's own issue template where one exists. Use when asked to "file an issue", "open an issue on <repo>", "report this bug upstream", "draft a bug report for <repo>", or when a bug surfaces mid-conversation that belongs on a repo the user doesn't maintain here. Always asks for the target repo first and always shows the drafted issue for confirmation before creating it — never posts to GitHub without that confirmation. Pairs with the `issue-verify` skill, which can pick up the issue once it's filed.
Turn an `issue-verify` checkpoint commit into an actual fix. Locates the failing test behind the `eddeee888:oss:issue-verify` marker (same branch or a different one), root-causes it, works out whether the bug lives in this library or in a dependency, presents the user 2-3 concrete fix options with pros/cons, then implements whichever they pick — building directly on top of the checkpoint commit — and pushes it as a draft PR marked `eddeee888:oss:issue-fix`. Use when asked to "fix issue
Verify a GitHub issue is real and reproducible before any fix work starts. Checks the issue for a reproduction, asks the reporter for one if it's missing (using the repo's own issue template as the guide), writes a test that encodes the repro, and — once that test is confirmed failing for the right reason — pushes it, still failing, as a checkpoint commit marked `eddeee888:oss:issue-verify`. Use when asked to "verify issue
Plugin manifests1
{
"name": "oss",
"description": "Skills for maintaining and contributing to open source projects — issue triage, release notes, changelog management, contribution guidelines, and similar."
}For maintainers
If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.
[oss on Agent Plugins Marketplace](https://pluginsmp.com/plugins/oss)