Claude Skills by paperclipai

Transform an output-focused roadmap into an outcome-focused one that communicates strategic intent. Rewrites initiatives as outcome statements reflecting user and business impacts

Perform a PESTLE analysis covering Political, Economic, Social, Technological, Legal, and Environmental factors

Perform Porter's Five Forces analysis — competitive rivalry, supplier power, buyer power, threat of substitutes, and threat of new entrants

Brainstorm product positioning ideas differentiated from competitors. Identifies top competitors and generates positioning statements with rationale

Run a pre-mortem risk analysis on a PRD or launch plan. Categorizes risks as Tigers (real problems), Paper Tigers (overblown concerns), and Elephants (unspoken worries), then classifies as launch-b...

Analyze and design pricing strategies including pricing models, competitive pricing analysis, willingness-to-pay estimation, and price elasticity

Reference guide to 9 prioritization frameworks with formulas, when-to-use guidance, and templates — RICE, ICE, Kano, MoSCoW, Opportunity Score, and more

Prioritize assumptions using an Impact × Risk matrix and suggest experiments for each

Prioritize a backlog of feature ideas based on impact, effort, risk, and strategic alignment with top 5 recommendations

Draft a detailed privacy policy covering data types, jurisdiction, GDPR and compliance considerations, and clauses needing legal review

Brainstorm 5 unique, memorable product names with rationale aligned to brand values and target audience

Create a comprehensive product strategy using the 9-section Product Strategy Canvas — vision, segments, costs, value propositions, trade-offs, metrics, growth, capabilities, and defensibility

Brainstorm an inspiring, achievable, and emotional product vision that motivates teams and aligns stakeholders

Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes)

Comprehensive PM resume review and tailoring against 10 best practices including XYZ+S formula, keyword optimization, job-specific tailoring, and structure

Analyze user feedback data to identify segments with sentiment scores, JTBD, and product satisfaction insights

Generate SQL queries from natural language descriptions

Build a stakeholder map using a power/interest grid, identify communication strategies per quadrant, and generate a communication plan

Generate a Startup Canvas combining Product Strategy (9 sections) and Business Model (costs + revenue) for a new product. An alternative to BMC and Lean Canvas that separates strategy from business...

Summarize a customer interview transcript into a structured template with JTBD, satisfaction signals, and action items

Summarize a meeting transcript into structured notes with date, participants, topic, key decisions, summary points, and action items

Perform a detailed SWOT analysis — strengths, weaknesses, opportunities, and threats with actionable recommendations

Create comprehensive test scenarios from user stories with test objectives, starting conditions, user roles, step-by-step actions, and expected outcomes

Create refined user personas from research data — 3 personas with JTBD, pains, gains, and unexpected insights

Segment users from feedback data based on behavior, JTBD, and needs. Identifies at least 3 distinct user segments

Create user stories following the 3 C's (Card, Conversation, Confirmation) and INVEST criteria with descriptions, design links, and acceptance criteria

Generate value proposition statements for marketing, sales, and onboarding from existing value propositions

Design a detailed value proposition using a 6-part JTBD template — Who, Why, What before, How, What after, Alternatives

Create product backlog items in Why-What-Acceptance format — independent, valuable, testable items with strategic context

GitHub Actions workflow for automated pragmatic code review on pull requests, posting triage-leveled findings as PR comments

GitHub Actions integration for automated design review on pull requests that modify frontend files

Perform a 7-tier hierarchical code quality review covering Architecture, Functionality, Security, Maintainability, Testing, Performance, and Dependencies with triage levels (Critical/Blocker, Improvement, Nit)

GitHub Actions workflow for automated security review on pull requests with confidence-gated PR comments

Perform a focused 3-phase security review with vulnerability identification, false-positive filtering, and confidence scoring (>80% exploitability threshold) covering Input Validation, Auth, Crypto, Injection, and Data Exposure

Update the root README.md with entries for new or changed agent companies. Use when a new company has been added to the repo, when company details have changed (agents added/removed, skills added/removed), or when the user asks to refresh/sync the README. Triggers on: "update the readme", "add this company to the readme", "sync readme", "refresh readme", or after creating a new company with company-creator.

Explores user intent, requirements and design before implementation. Use before any creative work — creating features, building components, adding functionality, or modifying behavior.

Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies

Use when you have a written implementation plan to execute in a separate session with review checkpoints

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work — guides completion of development work by presenting structured options for merge, PR, or cleanup

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable — requires technical rigor and verification, not performative agreement or blind implementation

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

Use when executing implementation plans with independent tasks in the current session

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

Use when implementing any feature or bugfix, before writing implementation code

Use when starting feature work that needs isolation from current workspace or before executing implementation plans — creates isolated git worktrees with smart directory selection and safety verification

Use when starting any conversation — establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions

Use when about to claim work is complete, fixed, or passing, before committing or creating PRs — requires running verification commands and confirming output before making any success claims; evidence before assertions always

Use when you have a spec or requirements for a multi-step task, before touching code

Use when creating new skills, editing existing skills, or verifying skills work before deployment

Evaluate decisions across three time horizons: 10 minutes, 10 months, 10 years. Reveals when short-term thinking hijacks decisions and helps overcome present bias.