New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

First Maintainer Month

by mohitagw15856 in mohitagw15856/pm-claude-skills

Set up a new open-source project's first month so it can grow without eating its maintainer — the README that routes people correctly, CONTRIBUTING boundaries written before there are contributors…

MITAuto-check passedDevelopment

Install First Maintainer Month

skills CLI
$ npx skills add mohitagw15856/pm-claude-skills --skill first-maintainer-month -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install mohitagw15856/pm-claude-skills first-maintainer-month --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/first-maintainer-month .claude/skills/first-maintainer-month && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
first-maintainer-month
GitHub stars
1.4k
Token cost
~1.5k tokens
SKILL.md length
689 words
Files
1
Skills in repo
1,348
Repo updated
First seen
Licence
MIT

At a glance

Set up a new open-source project's first month so it can grow without eating its maintainer — the README that routes people correctly, CONTRIBUTING boundaries written before there are contributors…

  • Works in 5 steps: README routes, not sells. One-line… → CONTRIBUTING sets the vision line early.… → Templates do the triage. Bug: version,… → …
  • Someone says my repo is getting attention
  • SKILL.md covers What This Skill Produces, Required Inputs, Framework and Output Format, plus 4 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

First Maintainer Month is an agent skill from mohitagw15856/pm-claude-skills. Set up a new open-source project's first month so it can grow without eating its maintainer — the README that routes people correctly, CONTRIBUTING boundaries written before there are contributors, issue templates that pre-triage, a release rhythm, and the sustainability defaults (what you owe no one). Use when someone says 'my repo is getting attention', 'I just open-sourced something', 'set up my project properly', or their first PR from a stranger just landed. Produces the docs set, the templates, and the…

Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development. The repository describes itself as: 1255 professional Agent Skills for Claude, ChatGPT, Gemini, Cursor & Codex — PRDs, postmortems, leases, medical bills, layoffs, go-bags, new countries. Plain markdown, MIT, in… The licence is MIT.

When your agent uses it

  • Someone says my repo is getting attention
  • I just open-sourced something
  • Set up my project properly
  • Their first PR from a stranger just landed

Example prompts

  • “my repo is getting attention”
  • “I just open-sourced something”
  • “set up my project properly”
  • “/first-maintainer-month”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. README routes, not sells. One-line what-it-is → 60-second quickstart
  2. CONTRIBUTING sets the vision line early. One paragraph on what the
  3. Templates do the triage. Bug: version, repro steps, expected/actual
  4. Release rhythm beats release pressure. State the stance in README
  5. Month-one routine, sized honestly. A fixed weekly block

What it can do on your machine

Read from SKILL.md and the folder at commit 1cbf1f0. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

First Maintainer Month loads about 1.5k tokens when it runs. Until then it costs about 139 tokens; SKILL.md has 689 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~139
When it runs · the whole SKILL.md, loaded when a task matches
~1.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from mohitagw15856/pm-claude-skills at commit 1cbf1f0, republished under its MIT licence (© mohitagw15856). 689 words, ~1,535 tokens.

Download SKILL.mdSave it as .claude/skills/first-maintainer-month/SKILL.md (or your agent's skills folder).
name
first-maintainer-month
description
Set up a new open-source project's first month so it can grow without eating its maintainer — the README that routes people correctly, CONTRIBUTING boundaries written before there are contributors, issue templates that pre-triage, a release rhythm, and the sustainability defaults (what you owe no one). Use when someone says 'my repo is getting attention', 'I just open-sourced something', 'set up my project properly', or their first PR from a stranger just landed. Produces the docs set, the templates, and the month-one routine.

First Maintainer Month Skill

The transition from "my code, public" to "a project with users" happens in one surprising week — the first stranger's issue, the first PR, the first demand — and the habits set in that month harden into the project's culture. Most maintainer burnout traces back to boundaries never written: no CONTRIBUTING to point at, no issue template doing the pre-triage, no stated release rhythm, and an implicit promise of instant response that was never sustainable. This skill sets the defaults while they're cheap: documents that route people, templates that filter, and the load-bearing sentence every new maintainer needs in writing — this is a volunteer project; responses happen when they happen.

What This Skill Produces

  • A README restructure: what it does in one line, quickstart, the support-expectations paragraph, and where everything else routes
  • CONTRIBUTING.md written for a project with 0–5 contributors: what's welcome, what needs an issue first, the vision line that powers future nos, PR standards kept minimal
  • Issue/PR templates that pre-triage: bug template demanding the repro, feature template asking "why does this belong here?", the config that routes questions to discussions
  • The release rhythm: versioning stance, a changelog habit ([[changelog-generator]] plugs in), and "releases happen when ready, not on demand"
  • The month-one routine + sustainability defaults: response-time expectations stated publicly, the co-maintainer bar, the walk-away clause (archiving honestly is always allowed)

Required Inputs

Ask for (if not already provided):

  • The project: what it does, current traction (stars/users/issues so far), license already chosen or not
  • The maintainer's real intent: hobby, portfolio, hoping-it-grows, or accidentally-load-bearing — the boundary strength scales with this
  • Honest available hours per week, and the response-time promise they can actually keep (then halve it)
  • What they dread most (drive-by demands? bad PRs? being ignored?) — the docs pre-answer the dread

Framework

  1. README routes, not sells. One-line what-it-is → 60-second quickstart → the honesty block: project status (active/hobby/experimental), support expectations ("volunteer-maintained; issues answered in batches"), links to CONTRIBUTING/discussions. The honesty block is the burnout vaccine — written now, it's context; written after complaints, it's defensive.
  2. CONTRIBUTING sets the vision line early. One paragraph on what the project deliberately is and isn't — this sentence powers every future [[the-maintainers-no]]. Then: bugs welcome with repro · features need an issue before a PR · small PRs merge fast, big surprise PRs mostly don't · the courtesy note that maintainer time is the scarce resource.
  3. Templates do the triage. Bug: version, repro steps, expected/actual — incomplete reports get the template pointed at, kindly, once. Feature: the problem before the solution, and "would this belong in core or a plugin?" Questions route to Discussions so the issue queue stays a work queue.
  4. Release rhythm beats release pressure. State the stance in README: semver-ish, changelog kept, releases batched ("roughly monthly when there's something to ship"). A stated rhythm converts "when will this release??" from pressure into a known answer.
  5. Month-one routine, sized honestly. A fixed weekly block ([[maintainer-triage]]'s 30 minutes) · respond in batches, never on arrival (arrival-response trains the crowd to expect it) · say the walk-away clause out loud once: archiving a project honestly served is a legitimate ending, and knowing that is what makes continuing a choice.
Show full SKILL.md (168 more words)Show less

Output Format

## README restructure
[The new skeleton with the honesty block drafted verbatim]

## CONTRIBUTING.md (ready to commit)
[Vision line · what's welcome · issue-before-PR · PR standards]

## Templates (.github/)
[bug_report.yml · feature_request.yml · config.yml routing questions]

## Release stance (paste into README)
[Versioning · changelog habit · the rhythm sentence]

## Month one
[Weekly block · batch-response rule · the three habits · walk-away clause]

Quality Checks

  • The support-expectations paragraph exists and matches the maintainer's real hours (halved), not their guilt
  • The vision line is specific enough to justify a concrete future no
  • Bug template demands repro; feature template demands the problem
  • Everything fits a 0-contributor project today — no governance LARP (CoC yes; steering committees no)
  • The walk-away clause appears — sustainability includes the exit

Anti-Patterns

  • Do not import big-project governance onto a two-week-old repo — process should trail traction, not lead it
  • Do not promise response times the maintainer can't keep on a bad month — under-promise in writing
  • Do not write CONTRIBUTING as a wall of rules; it's a welcome with boundaries, in that order
  • Do not let the first demanding user set the culture — the docs exist so the maintainer's defaults win

[[maintainer-triage]] when the backlog arrives; [[the-maintainers-no]] for the moments docs can't pre-answer; [[changelog-generator]] and [[pr-description-writer]] for the release rhythm's moving parts.

Example Trigger Phrases

  • "My repo is getting attention."
  • "I just open-sourced something."
  • "Set up my project properly."

© mohitagw15856, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/first-maintainer-month of mohitagw15856/pm-claude-skills.

Open the folder on GitHubat commit 1cbf1f0

Compare with similar skills

First Maintainer Month next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

First Maintainer Month compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
First Maintainer Month this skillmohitagw15856/pm-claude-skills1.4k—~1.5kAutomated safety check: PassMIT
Vercel Composition Patternssupabase/supabase111k58 repos~726Automated safety check: PassMIT
Finishing a Development Branchobra/superpowers297k5 repos~1.9kAutomated safety check: PassMIT
Typescript Advanced Typesrolling-scopes/rsschool-app10k25 repos~4.2kAutomated safety check: PassMPL-2.0
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Code Review ChecklistshareAI-lab/learn-claude-code78k4 repos~1.1kAutomated safety check: PassMIT

Similar skills

  • Vercel Composition Patterns

    supabase/supabase

    Official

    React composition patterns that scale. An agent skill from supabase/supabase.

    111k GitHub starsUsed in 58 repos~726 tokens
    DevelopmentAuto-check passed

  • Finishing a Development Branch

    obra/superpowers

    Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.

    297k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed

  • Typescript Advanced Types

    rolling-scopes/rsschool-app

    Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications.

    10k GitHub starsUsed in 25 repos~4.2k tokens
    DevelopmentAuto-check passed

  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed

  • Code Review Checklist

    shareAI-lab/learn-claude-code

    Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.

    78k GitHub starsUsed in 4 repos~1.1k tokens
    DevelopmentAuto-check passed

  • Greploop

    onyx-dot-app/onyx

    Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until Greptile gives it a 5/5 confidence score with zero unresolved comments.

    32k GitHub starsUsed in 4 repos~3.3k tokens
    DevelopmentAuto-check passed

More from mohitagw15856/pm-claude-skills

All 1,348 skills in this repo

  • Car Tco

    mohitagw15856/pm-claude-skills

    Compare the total cost of car ownership across buy-new, buy-used, lease, and keep-your-current-car — depreciation, insurance, maintenance ramp, and fuel over a real horizon, not just the monthly…

    1.4k GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed

  • Cs Health Scorecard

    mohitagw15856/pm-claude-skills

    Build a customer health scorecard for a specific account. An agent skill from mohitagw15856/pm-claude-skills.

    1.4k GitHub stars~2.4k tokensUpdated yesterday
    Auto-check passed

  • Exit Waterfall

    mohitagw15856/pm-claude-skills

    Compute who gets what at each exit price from a cap table — liquidation preferences, conversion points, and where the founders' share collapses.

    1.4k GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed

  • Feature Prioritisation

    mohitagw15856/pm-claude-skills

    Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items.

    1.4k GitHub stars~2k tokensUpdated yesterday
    Auto-check passed

  • Fire Number

    mohitagw15856/pm-claude-skills

    Compute a financial-independence (FIRE) target and years-to-reach with every assumption labeled as an assumption — plus a sensitivity table instead of a single false-precision answer.

    1.4k GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed

  • Freelance Rate

    mohitagw15856/pm-claude-skills

    Derive a freelance day/hourly rate backwards from target income, honest billable utilization, overhead, and the self-employment tax premium — the arithmetic that proves a rate is not salary÷2000.

    1.4k GitHub stars~1.2k tokensUpdated yesterday
    Auto-check passed

Categories

Questions about First Maintainer Month

What does First Maintainer Month do?

Set up a new open-source project's first month so it can grow without eating its maintainer — the README that routes people correctly, CONTRIBUTING boundaries written before there are contributors…. First Maintainer Month is an agent skill from mohitagw15856/pm-claude-skills. Set up a new open-source project's first month so it can grow without eating its maintainer — the README that routes people correctly, CONTRIBUTING boundaries written before there are contributors, issue templates that pre-triage, a release rhythm, and the sustainability defaults (what you owe no one).

When should I use First Maintainer Month?

First Maintainer Month fits situations like: someone says my repo is getting attention; I just open-sourced something; set up my project properly; their first PR from a stranger just landed.

How do I install First Maintainer Month in Claude Code?

Run `npx skills add mohitagw15856/pm-claude-skills --skill first-maintainer-month -a claude-code`. Or copy the skill folder (skills/first-maintainer-month in mohitagw15856/pm-claude-skills) into .claude/skills/first-maintainer-month in your project. Claude Code loads it when a task matches its description.

How do I install First Maintainer Month in Codex?

Run `npx skills add mohitagw15856/pm-claude-skills --skill first-maintainer-month -a codex`. Or copy the skill folder (skills/first-maintainer-month in mohitagw15856/pm-claude-skills) into .agents/skills/first-maintainer-month in your project. Codex loads it when a task matches its description.

Can I use First Maintainer Month in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mohitagw15856/pm-claude-skills --skill first-maintainer-month -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/first-maintainer-month, .gemini/skills/first-maintainer-month, .github/skills/first-maintainer-month and .opencode/skills/first-maintainer-month in your project.

What does First Maintainer Month need to run?

SKILL.md names no scripts, command-line tools or credentials: First Maintainer Month is instructions for the agent only.

Does First Maintainer Month access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is First Maintainer Month safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does First Maintainer Month use?

First Maintainer Month is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does First Maintainer Month use?

About 1.5k tokens (SKILL.md is roughly 6.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to First Maintainer Month?

Skills that share tags, products or a category with First Maintainer Month: Vercel Composition Patterns (supabase/supabase, 111k stars), Finishing a Development Branch (obra/superpowers, 297k stars), Typescript Advanced Types (rolling-scopes/rsschool-app, 10k stars) and PR Babysitter (openinterpreter/openinterpreter, 69k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains First Maintainer Month?

mohitagw15856 (a GitHub user) maintains it in mohitagw15856/pm-claude-skills, which has 1,434 GitHub stars. The repository holds 1,348 skills in this directory. The repository was last updated on October 9, 2026.

Source: mohitagw15856/pm-claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.