Menu

Individual skill

first-maintainer-month

0upvotes

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.

plugins/pm-maintainer/skills/first-maintainer-month/SKILL.md

Read pinned source

Source commit f7c90bc09ee05dc25cf257bdb1826f2c2552c2cb

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 9, 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,539
Repository last updated
Nov 10, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# 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
Back to top