Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Open Source Maintainer Kit

    1

    Drafts comprehensive CONTRIBUTING.md files covering environment setup, branch conventions, and review processes.

    $9.99

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Open Source Maintainer Kit

    Open Source Maintainer Kit

    Example session with this skill installed

    I have a Rust CLI tool for log analysis. It's getting popular but the bug reports are messy. Create an issue template and a PR template to improve the quality of contributions.

    • Read your context and instructions
    • Compiled the open source maintainer

    I have generated structured templates tailored for your Rust CLI tool to ensure contributors provide environment details and test coverage.

    Repository Templates

    Bug Report Template (.github/ISSUE_TEMPLATE/bug_report.md)

    ---
name: Bug report
about: Create a report to help us improve
title: '[BUG] '
labels: bug, triage
assignees: ''
---

**Describe the bug**
A clear and concise description of what the bug is.

**Reproduction Steps**
1. Run `log-analyzer --input sample.log`
2. See error '...'

**Expected behavior**
A clear description of what you expected to happen.

**Environment info**
- OS: [e.g. Ubuntu 22.04, macOS Sonoma]
- Rust version: `rustc --version`
- Tool version: `log-analyzer --version`

**Additional context**
Add any other context, log snippets, or screenshots about the problem here.

    Pull Request Template (.github/pull_request_template.md)

    
## Summary
Describe the changes introduced by this PR. Include motivation and context.

## Related Issue
Fixes # (issue)

## Type of Change
- [ ] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

## Checklist
- [ ] I have run `cargo fmt` and `cargo clippy`.
- [ ] I have added tests that prove my fix is effective or that my feature works.
- [ ] I have updated the documentation (README.md or /docs).
- [ ] My changes generate no new warnings.

    Next steps

    1. Create the .github/ISSUE_TEMPLATE directory in your root.
    2. Save the Bug Report content as bug_report.md inside that folder.
    3. Save the PR template as pull_request_template.md directly in the .github folder.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    The problem

    Maintainers of open-source projects often lose hours to low-quality bug reports, vague pull requests, and repetitive contributor onboarding questions. Without structured documentation, scaling a project leads to maintainer burnout and contributor friction.

    What it does

    • Generates repository-ready issue templates for bug reports, feature requests, and performance regressions.
    • Creates pull request guides with standardized checklists for testing, documentation, and breaking changes.
    • Drafts comprehensive CONTRIBUTING.md files covering environment setup, branch conventions, and review processes.
    • Produces maintainer workflow documentation including triage rules, label systems, and release checklists.
    • Constructs sponsor messaging and funding copy to help projects communicate value and maintenance needs.

    Why this beats prompting it yourself

    General-purpose LLMs often produce generic "fill in the blank" templates that don't address real-world maintainer burdens. This skill focuses on enforceable boundaries and triage-efficient structures that reduce noise and prevent over-promising maintainer availability.

    Use cases

    • Standardizing a new repository before its first public release.
    • Auditing existing contributor docs to identify friction points and triage bottlenecks.
    • Scaling a solo project into a community-maintained tool with clear governance.
    • Drafting release notes and sponsor tiers for a mature utility.

    Known limitations

    Does not provide legal advice on licenses, contributor license agreements (CLAs), or tax implications of sponsorships.</

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Technical Documentation.

    Does not provide legal advice on licenses, governance, or tax status. Cannot automate community moderation or perform security audits.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 2 months ago

    Software
    Python

    Permissions

    No special permissions declared or detected

    Listed2 months ago

    What's inside

    Frequently Asked Questions

    This skill automates the creation of professional-grade repository documentation, including customized issue templates, PR checklists, contribution guides, and maintainer workflows designed to reduce noise and prevent burnout.

    The kit provides Markdown-formatted files that are compatible with any platform supporting standard documentation, such as GitHub, GitLab, and Bitbucket.

    You will receive a comprehensive suite of documentation templates, including CONTRIBUTING.md, issue and pull request templates, community standards, release note drafts, and sponsor messaging assets.

    No, this skill is designed for ease of use; you simply provide your project's context, and it generates ready-to-use Markdown text that you can copy directly into your repository.

    While the skill provides excellent templates for community standards and conduct, it does not offer legal advice regarding software licenses, CLAs, or the tax implications of project sponsorships.

    New in Technical Documentation