Index of every page on this site: llms.txt
All skills
masihmoafi avatar

/contribution-checklist

@c0a5d13
by Masih Moafimasihmoafi/skills10 stars
Run it yourself

Use when preparing or reviewing a contributor issue, call for participation, newsletter submission or related outreach, or answering a reviewer's feedback on one.

  • 1 file
  • 1.6 KB
  • Updated 3 weeks ago
  • GitHub
Use this Skill: https://skilld.dev/gh/masihmoafi/skills/contribution-checklist

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈47 tokens for metadata: the name and description. ≈350 when used: this file.

Description uses 2.3% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈187 characters, or 2.3%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Contribution Checklist

Make a contribution request clear to someone who knows neither the project nor the conversation.

State the ask first

Open with who should do what and the expected result; put background after it. Read the destination's current submission guidance and pick the section that fits: an editor publishes an update or link, a developer implements a change, a tester reproduces a behavior. Marketing is an objective, not an implementation task: do not quietly turn it into feature recruitment, and never invent work only to qualify for coverage.

Before submitting, answer the three questions from Nell Shamrell-Harrington's review:

  • What is the ask? One bounded change, its observable result, and what is out of scope.
  • Where does someone start? Current links to the actual files or functions, the shortest setup and reproduction steps, and a first increment proportional to the stated difficulty.
  • Is mentoring available? Who answers questions and reviews changes, or that nobody does. Never promise someone else's time.

Answer reviewer feedback

Answer the reviewer's concrete questions, acknowledge what was unclear, and point to the actual revisions. Do not answer a request for a bounded task with a general wish for traction, stars, or feature parity.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No third-party reports yet.

Signed by skilld at c0a5d13. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last week.

Activeupdated 3 weeks ago

README badge

README badge for masihmoafi/skills/contribution-checklist