Skip to content

CONTRIBUTING.md

Latest commit

 

History

History
162 lines (118 loc) · 3.29 KB

CONTRIBUTING.md

File metadata and controls

162 lines (118 loc) · 3.29 KB

Contributing to GTM Skills

Thanks for improving these skills. Here's how to contribute effectively.

What to Contribute

1. New Frameworks

Add systematic approaches missing from existing skills.

Good contributions:

  • Decision trees with clear criteria
  • Checklists for repeatable processes
  • Templates that save time
  • Quantified thresholds (e.g., "deprioritize if <5 customers after 12 months")

Not helpful:

  • Generic advice without structure
  • Personal opinions without validation
  • Frameworks that duplicate existing content

2. Real Scenario Examples

Add concrete examples that demonstrate framework application.

Format:

**Example: [Brief title]**
- Context: [Company size, industry, challenge]
- Framework applied: [Which framework from the skill]
- Result: [What happened, what was learned]

3. Templates & Checklists

Add actionable tools that make frameworks easier to use.

Examples:

  • Partnership charter template
  • Mutual action plan spreadsheet
  • Health scoring rubric
  • Stakeholder mapping worksheet

Skill Structure

Each skill follows this format:

---
name: skill-name
description: Brief description with triggers and use cases
---

# [Skill Name]

[One-sentence value prop]

## When to Use
- Trigger patterns
- Context where skill applies

## Core Frameworks
### Framework 1: [Name]
- Systematic methodology
- Step-by-step process
- Decision criteria

## Decision Trees
Clear if/then logic for common decisions

## Quick Reference
Checklists for quick application

Don't:

  • Change structure without discussion
  • Add content outside these sections
  • Embed marketing fluff or product pitches

How to Contribute

Small Changes (typos, clarifications)

  1. Fork repo
  2. Make changes
  3. Submit PR with clear description

New Frameworks or Sections

  1. Open an issue first to discuss
  2. Get feedback on structure
  3. Submit PR once aligned

New Skills

  1. Open an issue proposing the skill
  2. Share outline and key frameworks
  3. Submit draft for review
  4. Iterate based on feedback

Quality Standards

Good frameworks:

  • Systematic (not ad-hoc)
  • Actionable (specific steps)
  • Validated (used in production)
  • Comprehensive (covers edge cases)

Good writing:

  • Clear and direct
  • No marketing speak
  • No unnecessary jargon
  • Scannable structure

Testing: Test new frameworks with 3-5 real scenarios before submitting. Does the framework:

  1. Provide clear answers?
  2. Prevent common mistakes?
  3. Save time vs figuring it out yourself?

Review Process

  1. Triage - Maintainers review issue/PR within 48 hours
  2. Feedback - Provide suggestions for improvement
  3. Iteration - Contributor updates based on feedback
  4. Merge - Accepted once quality bar is met

Rejection reasons:

  • Doesn't fit skill scope
  • Duplicates existing content
  • Lacks systematic structure
  • Not validated in real usage

Code of Conduct

Do:

  • Share knowledge generously
  • Give constructive feedback
  • Credit sources appropriately
  • Iterate based on feedback

Don't:

  • Promote specific products/companies
  • Copy copyrighted material
  • Argue about rejected PRs
  • Add self-promotional links

Questions?

Open an issue labeled question and maintainers will respond.

Thank you for making GTM skills better.