mohitagw15856/contributor-guide
skills/contributor-guide/SKILL.md
Write a CONTRIBUTING guide that helps people contribute to an open-source project without friction. Use when asked to write a CONTRIBUTING.md, set up contribution guidelines, or make a repo welcoming to contributors. Produces a clear guide: how to set up, the contribution workflow, standards, PR expectations, and how to get help — lowering the barrier to a first PR.
$ install --global
skillsauthnpx skillsauth add mohitagw15856/pm-claude-skills contributor-guideInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jul 1, 2026, 7:56 AM39.3s1 file scanned
SKILL.md
- name:
- contributor-guide
- description:
- Write a CONTRIBUTING guide that helps people contribute to an open-source project without friction. Use when asked to write a CONTRIBUTING.md, set up contribution guidelines, or make a repo welcoming to contributors. Produces a clear guide: how to set up, the contribution workflow, standards, PR expectations, and how to get help — lowering the barrier to a first PR.
Contributor Guide Skill
Most would-be contributors give up at setup friction or unclear expectations. A good CONTRIBUTING.md removes
the guesswork: how to get the project running, how to propose a change, what a mergeable PR looks like, and
where to ask. This skill writes that guide — welcoming, specific, and aimed at getting someone to a successful
first PR.
Required Inputs
Ask for these only if they aren't already provided:
- Project & stack — what it is, language/framework, repo layout basics.
- Dev setup — how to clone, install, run locally, and run tests.
- Workflow — branch model, commit/PR conventions, where issues live, who reviews.
- Standards — linting/formatting, test requirements, the Code of Conduct (link).
- Norms (optional) — how decisions are made, response times, good-first-issue process.
Output Format
A CONTRIBUTING.md:
Contributing to [Project]
A warm one-liner: contributions are welcome, here's how to make it smooth.
Ways to contribute — issues, docs, code, triage — not everyone writes code.
Development setup
# clone, install, run, test — the exact commands
…so a contributor can get the project running and tests passing locally.
Finding something to work on — point to good first issue / help wanted; ask people to comment before starting larger work.
Making a change (the workflow)
- Branch from … with naming convention …
- Make the change; follow the standards below.
- Add/update tests; run the linter/tests locally.
- Open a PR — what the PR description should include; link the issue.
Standards — formatting/linting, test expectations, commit/PR conventions, the Code of Conduct link.
What happens next — who reviews, rough turnaround, how feedback works.
Getting help — where to ask (Discussions, chat, issue) — make it explicitly OK to ask.
Quality Checks
- [ ] Setup commands actually get the project running and tests passing
- [ ] The contribution workflow is numbered and unambiguous (branch → change → test → PR)
- [ ] Standards (lint, tests, commit/PR conventions, CoC) are stated and linked
- [ ] It points to good-first-issues and welcomes non-code contributions
- [ ] It's encouraging in tone and tells people exactly where to get help
Anti-Patterns
- [ ] Do not assume the contributor knows the setup — spell out the exact commands
- [ ] Do not leave PR expectations implicit — say what a mergeable PR includes
- [ ] Do not be gatekeep-y or cold — friction and tone both lose contributors
- [ ] Do not omit how to get help or who reviews — uncertainty stalls first PRs
- [ ] Do not forget the Code of Conduct link — it sets the community standard
Based On
Open-source contribution best practices (clear setup, defined workflow, good-first-issues, welcoming tone, CoC).
Related Skills
mohitagw15856/win-loss-analysis
business
VerifiedTrustedCommunity
Analyze why deals are won and lost and turn it into an action plan. Use when asked to run a win/loss analysis, review closed-won and closed-lost deals, understand why the team is losing to a competitor, or summarize sales feedback into patterns. Produces a structured win/loss report with themes, win/loss rates by segment and competitor, representative quotes, and prioritized actions for product, marketing, and sales.
1,117SKILL.mdUpdated Jul 2, 2026
mohitagw15856/which-skill
development
VerifiedTrustedCommunity
Route a fuzzy request to the right skill in this library. Use when the user is unsure which skill fits, asks 'which skill should I use for X', describes a task without naming a skill, or when a request could plausibly match several skills. Produces a best-fit recommendation with the inputs to gather, a runner-up with the tie-breaker, and a workflow recipe when the job spans multiple skills.
1,117SKILL.mdUpdated Jul 2, 2026
mohitagw15856/vuln-triage
testing
VerifiedTrustedCommunity
Triage a vulnerability or scanner finding — assess real severity, exploitability, and how urgently to fix. Use when asked to triage a CVE, prioritize scanner/pentest findings, assess a vuln's risk, or decide what to patch first. Produces a triage verdict: CVSS-informed severity adjusted for your context, exploitability, real risk, a fix/mitigation, and an SLA — so you fix what matters, not just what's red.
1,117SKILL.mdUpdated Jul 2, 2026
mohitagw15856/voice-of-customer-program
development
VerifiedTrustedCommunity
Stand up a Voice of Customer (VoC) program that turns feedback into action. Use when asked to build a VoC program, design a customer feedback loop, consolidate feedback sources, or set up a closed-loop feedback process. Produces a VoC program design — objectives, feedback sources and channels, a taxonomy, collection and analysis cadence, closed-loop routing, ownership, and success metrics.
1,117SKILL.mdUpdated Jul 2, 2026