SkillAgentSearch skills...

oss-contribution-research

Research and prepare an outside contribution to an open-source repo, then stop at a queue item for a human to approve: policy check, intake, duplicate check, reproduction, patch, the repo's own checks, an independent critic rerun, and a disclosed, hashed draft of the exact text to post.

Install / Use

npx skills add rampstackco/claude-skills --skill oss-contribution-research

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

86/100

Category

Automation

Supported Platforms

Universal

Tags

Our assessment of oss-contribution-research

oss-contribution-research scores 86/100 on our quality scale, 1835th of 2,790 Automation skills we index.

Its SKILL.md is 19 KB long, well organised into 9 sections and no code examples: a thorough specification that gives an agent plenty to work with.

It has 902 GitHub stars, a meaningful sign that others use it.

Substance
30/30
Structure
13/20
Description
15/15
Adoption
13/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so oss-contribution-research is actively maintained.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-11-10. Automated pattern scan on 2026-11-10. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

oss-contribution-research compared with similar skills

All 4 of these similar skills score higher than oss-contribution-research; compare them before choosing.

SkillScoreStarsUpdatedFormat
oss-contribution-research (this skill)by rampstackco869022mo agoSKILL.md
Agent-Reachby Panniantong100112.3k8d agoCLAUDE.md
rufloby ruvnet10081.9ktodayCLAUDE.md
Claude-Code-Game-Studiosby Donchitos10039.7k7d agoCLAUDE.md
Scraplingby D4Vinci100103.6k2d agoMCP Server

Frequently asked questions

How do I install oss-contribution-research?
Run npx skills add rampstackco/claude-skills --skill oss-contribution-research. The install tabs above show the steps for each supported agent.
Which AI agents does oss-contribution-research work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is oss-contribution-research safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is oss-contribution-research still maintained?
The repository was last updated about 2 months ago, so oss-contribution-research is actively maintained.

name: oss-contribution-research description: "Research and prepare an outside contribution to an open-source repo, then stop at a queue item for a human to approve: policy check, intake, duplicate check, reproduction, patch, the repo's own checks, an independent critic rerun, and a disclosed, hashed draft of the exact text to post. Use this skill whenever the user wants to contribute to someone else's repo, fix an upstream bug, pick up a good-first-issue, draft an AI-assisted pull request for an outside project, follow up on their own outside PR, or run a gated contribution pipeline. Triggers on open source contribution, contribute to this repo, upstream fix, outside PR, external PR, good first issue, fix this issue in their repo, contribution research, AI-assisted PR, disclose AI in PR, reply to review on my PR. Also triggers when the user names an issue in a repo they do not maintain and asks for a fix, even if they do not say contribute." category: development catalog_summary: "Gated research and patch prep for outside open-source PRs, ending in a human-approved queue item" display_order: 5

OSS Contribution Research

Prepare one outside contribution to an open-source repo, gate by gate, and stop at a queue item a human approves. The agent running this skill never posts.


When to use

  • Picking up an existing issue or confirmed bug in a repo the user does not maintain
  • Checking whether a repo accepts AI-assisted pull requests before any work starts
  • Asking a maintainer for a go-ahead before writing a patch (an intake comment)
  • Turning a fix into a small, disclosed pull request draft that a human approves
  • Following up on the user's own outside pull request: a review reply, the 14-day ping, or the 28-day close
  • Running a contribution pipeline with an approval queue and a per-repo registry

When NOT to use

  • Reviewing a pull request in a repo the user maintains (use code-review-web)
  • Updating packages or lockfiles in the user's own project (use dependency-management)
  • Writing a new feature spec for the user's own product (use pm-spec-writing)
  • Writing a new skill for this catalog (use skill-creation-walkthrough)
  • Unsolicited refactors, rewrites, or features in someone else's repo. This skill refuses them.

Required inputs

  • Target. The repo (owner/repo) and one of: an existing issue or pull request URL, a bug the agent can reproduce, or a request to search the repo's open issues for a candidate.
  • Queue snapshot. Each run starts on the user's normal login. It makes read-only (GET) calls to the user's private approval queue repo and exports a snapshot to a local file. The snapshot holds three things:
    • the registry (registry.yaml), with each repo's policy class, disclosure template per action type, review mode, cadence cap, cached last submission date and status;
    • the posted ledger: issues labeled status:posted, with the poster's posted markers;
    • the pause state: whether any open issue is labeled pipeline:paused.
  • A read-only token. After the snapshot is written, the run switches to a read-only forge token for all outside research and patch work. It reads the queue only from the snapshot.
    • Filing. Filing the finished item into the queue is a separate, internal step on the user's normal login.
    • Posting. Posting to the outside repo happens only through the queue's poster, and only on approved items.
    • Freshness. The poster revalidates everything at post time, so the snapshot is never the last check.
  • A local clone of the target repo on a branch the user's fork can push later.
  • A local clone of the queue repo. The queue-item format, the poster's docs and its hash helper are read from the user's local clone of their private queue repo, pulled before the run. The read-only token cannot read that repo, so the run never fetches those files over it.

If the snapshot is missing, stop and ask for it. Do not infer a policy, a disclosure template, or a submission history.


The framework: gates in order, stop at the first fail

Each gate either passes with evidence or stops the run with a reason. A stop is a valid result. Report it; do not route around it.

  1. Pipeline gate. A pipeline:paused issue in the snapshot stops everything (kill switch).
  2. Repo gate. Classify the repo's AI-PR policy as allows, silent, or bans, with the cited line (see references/policy-classification.md). Stop on bans, and stop when the registry status is not active. Stop in each of these cases too, with no exception for a fuller review flow: an excluded repo stays excluded.
    • The policy requires the human owner to attest to reviewing the complete change.
    • The repo accepts issues but not pull requests.
    • The repo accepts pull requests only from members.
  3. Ownership gate. Before any throttle or duplicate check, classify the target as the user's own work or someone else's.
    • Own work. The user's own open pull request, or the user's own claim or intake comment on the issue. It routes to a follow-up item, not a block:
      • a review reply;
      • the 14-day ping (reply with purpose: ping);
      • the 28-day close (close);
      • after an approved intake, the pr item itself.
    • Competing work. Another person's PR, assignment, or claim. It goes to gate 5, which stops.
  4. Throttle and cadence gate. This gate applies to new pull requests only, not to replies or closes on the user's own work.
    • Stop if the user already has a different open pull request on this repo.
    • Stop if the cadence cap says the next submission is not due. Take the last submission date from the snapshot's posted ledger. The registry's date is a cached hint only; when the two disagree, the ledger wins.
  5. Duplicate and claim gate. Search open and closed pull requests and the issue thread. Stop on someone else's open pull request, assignment, or "working on this" comment.
    • Map open pull requests to issues from their bodies. List the open pull requests once (GET /repos/{owner}/{repo}/pulls?state=open&per_page=100, paginated) and read each body for the issues it names: "Fixes #n", "Closes #n", a bare #n, or an issue URL. The issue timeline endpoint's cross-referenced events are not returned on a read-only token, so an empty timeline proves nothing.
  6. Issue gate. Work only on an existing issue or a bug confirmed by reproduction. No unsolicited refactors or features.
    • Bug or small fix, from the body. Judge it from the issue body and thread. Labels are a hint only: a repo can have a bug label that none of its open bugs carry.
    • Still exists on the default branch. Check the current default branch, not only the issue's timeline. Search recent merged pull requests and commits that touch the relevant code, including ones that never link the issue. A -linked:pr filter misses them. Stop if the bug is already fixed; the issue is stale-open.
    • Claims are not facts. A bystander's "already resolved" or "can be closed" comment is a claim to verify against the code, not a result. It can cite the wrong commit and still reach the right conclusion, or the reverse.
  7. Intake gate. Where the repo asks for maintainer assignment, an accepted label, or a go-ahead, and none exists yet, the output is an intake queue item (a short comment asking to take the issue). No patch is written until the go-ahead arrives.
  8. Repro gate. A failing test or a documented reproduction exists before any fix. A pr item requires the real reproduction, captured as a repro record (see references/repro-record-template.md): target, surface, numbered steps, a measurable assertion with expected and observed values, a control that flips it, a second case, a regression check, environment, and evidence.
    • Browser reproductions need a connected browser tool. Reading the code and the fixtures is not a reproduction. Without a connected browser, the run may file intake items only; the pr item waits for a run that has one.
  9. Patch. The smallest single-purpose change that fixes the issue, in the repo's own style.
  10. Checks gate. The repo's own test suite and linters pass locally, at the commit that will be submitted.
  11. Size gate. The change is reviewable in under 5 minutes from a 3 to 5 sentence summary. If not, split it or drop it.
  12. Critic gate. A separate agent reruns the reproduction and the test suite itself, at the exact head commit, on a different model family where one is available. Re-reading the diff does not count. A critic fail blocks the item.
  13. Disclosure. Fill the item's structured Disclosure field from the registry template for this repo and this action type: pr_description, issue_comment, or review_reply (also used for a close).
    • none. The disclosure text is none.
    • unknown. Stop.
    • Template with slots. Fill every {slot} with what actually happened and put that exact line in the text to post (see references/pr-description-template.md).
    • No attribution. Where a repo forbids AI attribution, no tool name, trailer, or co-author line appears in the pull request body or in any commit.

Operating constraints that sit across every run:

  • Kill switch. Any close of the user's pull request that cites AI or low-quality automated work pauses that repo and the pipeline.
  • Stale rule. One polite ping at 14 days of maintainer silence, then a close at 28 days if still silent. Both are queue items the poster sends; neither is posted by hand.
  • Actions. The poster sends exactly four actions: intake, pr, reply, and close. Nothing outbound happens outside them.

Workflow

  1. Snapshot, then switch. On the user's normal login, export the queue snapshot (registry, posted ledger, pause state) with GET calls only. Then switch to the read-only token and confirm it is the one in use: gh api user names the expected account, and gh api rate_limit answers on that token.
    • Write-refusal probe: the user runs it, never the agent. Once per token, and again after any token renewal, the user runs a POST with no title to an issues endpoint on a repo of their own, for example gh api -X POST repos/<user>/<own-repo>/issues -f body=probe. A missing title means it cannot create a real issue. Expected: 403, so writes are refused. A 422 means the token can write; stop and replace it.
    • The agent does not run the probe, even if asked to retry it. If the user has not recorded a 403 for the current token, say so in the report and keep every call a GET.
    • Agent shells. Many agent shells start a fresh process per command, so a token set in one command is gone in the next. Start the agent from a terminal where the read-only token is already set.
  2. Run gates 1 to 3 from the snapshot, the repo's guidance files, and the target thread. Record each result with a link. If gate 3 finds the user's own work, draft the follow-up item and skip to step 9.
  3. Run gates 4 to 6 for new work. When the target is a candidate search, run them per candidate:
    • Listing. List with the issues endpoint (GET /repos/{owner}/{repo}/issues?state=open&sort=updated, core quota) and skip pull requests in the result. The search API has a secondary rate limit that can trip after a handful of calls.
    • Pool window. For a repo with more than 200 open issues, the pool is the 300 most recently updated items (three pages of 100). State the window in the report, with the date of the oldest update it reached, so later runs are comparable.
    • Order. Sort by recent update. Drop feature and docs proposals first, with a one-line reason each.
    • Screening. For each bug-shaped candidate, record the first failing gate and its evidence, then move on. Run the full gate set only on a candidate that has passed every earlier gate.
    • Result. The first candidate t

Truncated for display — read the full file on GitHub.

Related Skills

View on GitHub
GitHub Stars902
CategoryAutomation
Updated2mo ago
Forks124

Languages

JavaScript

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions
oss-contribution-research — Universal Skill: Install & Safety Check | SkillAgent