493 free skills
Project Management skills
Skills for project and team management — sprint planning, estimation, onboarding checklists, and standup/retro workflows.
Sourced from real, public repositories — synced daily, never invented.
493 free skills
Skills for project and team management — sprint planning, estimation, onboarding checklists, and standup/retro workflows.
Sourced from real, public repositories — synced daily, never invented.
15 tools across six categories
13 of them never send your data anywhere
Free · No signup · No trial clock
SEE THE DIRECTORY
jira
spillwavesolutions/jira
Manages JIRA issues, projects, and workflows using Atlassian MCP. Use when asked to "create JIRA ticket", "search JIRA", "update JIRA issue", "transition issue", "sprint planning", or "epic management".
icp-onboarding
growthenginenowoslawski/coldoutboundskills
Conversational intake for cold email campaigns. Interviews the user about their business, ICP (Ideal Customer Profile), offer, lead magnets, and hard vs soft filters. Outputs a structured `client-profile.yaml` that every other skill in the repo reads from. Use at the very start of a new campaign or when onboarding a new business. Triggers on "onboard me", "set up my ICP", "new client", "new business intake", "help me define my ICP".
customer-success-health-review
sylphxai/skills
Design and audit customer health scoring, onboarding success, adoption, renewal risk, expansion readiness, support signals, QBRs, lifecycle playbooks, and account success operations for SaaS, developer tools, marketplaces, and B2B products. Use when building customer success dashboards, health scores, churn risk reviews, renewal playbooks, or expansion motions.
fpf-problem-solving
codealive-ai/fpf-problem-solving-skill
First Principles Framework (FPF) — thinking amplifier. Use when user wants to think through a complex problem, architect a system, evaluate alternatives, decompose complexity, classify problems, define quality attributes, or plan rigorously. Also triggers on: FPF, bounded contexts, SoTA packs, assurance calculus, FPF Parts A-K. Not for simple task planning, general philosophy, or Agile unrelated to FPF.
in-product-education-review
sylphxai/skills
Design and audit in-product education, onboarding checklists, tooltips, empty-state guidance, contextual help, tours, templates, examples, nudges, feature discovery, upgrade education, and help-center handoffs. Use when a product needs to teach users without cluttering UI, blocking expert workflows, or becoming spammy growth messaging.
create-work-breakdown-structure
pjt222/agent-almanac
>
cost-estimator
aws-samples/sample-agent-skills-for-builders
Estimate AWS costs for CDK projects using real-time pricing data. Use when calculating infrastructure costs, generating pricing reports, or analyzing CDK resource costs before deployment.
spec-mining
alexander-danilenko/cortex-ai-skills
Apply this opinionated workflow when reverse-engineering legacy or undocumented systems: scope, explore with Glob/Grep/Read, trace data flows, document in EARS format, flag uncertainties. For code archaeology, onboarding, and requirements extraction.
scrum
krzysztofsurdy/code-virtuoso
Scrum framework fundamentals, sprint goal writing, and agile ceremony facilitation. Use when the user asks to plan a sprint, write sprint goals, facilitate daily scrums, run sprint reviews or retrospectives, define scrum roles, manage the product backlog, or apply agile estimation techniques. Covers the three pillars (transparency, inspection, adaptation), scrum artifacts, goal-writing templates (SMART, FOCUS, FAB), and team velocity tracking.
onboarding-summary
datadog-labs/agent-skills
Generate a live Single Step Instrumentation (SSI) onboarding confirmation report — verifies APM instrumentation is working end-to-end with deep links into the Datadog UI. Only use after agent-install and enable-ssi have both completed successfully.
linear-usage
fcakyon/claude-codex-settings
This skill should be used when user asks about "Linear issues", "issue tracking best practices", "sprint planning", "Linear project management", or "creating Linear issues".
cognitive-doc-design
gentleman-programming/gentle-ai
Design docs that reduce cognitive load. Trigger: writing guides, READMEs, RFCs, onboarding, architecture, or review-facing docs.
mobile-onboarding
nexu-io/html-anything
三个手机框并排: splash / value-prop / sign-in
progressive-estimation
sickn33/agentic-awesome-skills
Estimate AI-assisted and hybrid human+agent development work with research-backed PERT statistics and calibration feedback loops
research
openai/role-specific-plugins
Run fast, source-grounded UX research on the highest-signal problems users are experiencing with a user-specified digital product. Use when the user asks to research user pain, UX friction, onboarding issues, docs/help problems, developer experience friction, support pain, product workflow issues, or current user complaints for a named product.
sdd-constitution
alejandro-cedeno-10/agentic-sdd-kit
Author or update the project's constitution — openspec/project.md — the non-negotiable principles, conventions, and constraints the Spec-Driven Development flow must honor. Modeled on GitHub Spec-Kit's /constitution. Run once per repo when onboarding SDD, or whenever the team's principles change. The sdd-feature-flow Analyze gate checks every spec against it.
product-onboarding
skenetechnologies/plg-skills
When the user wants to design or improve new user onboarding -- including product tours, checklists, empty states, welcome flows, or progressive disclosure. Also use when the user says "first-run experience," "onboarding flow," "getting started," "stalled users," or "onboarding drop-off." For activation metrics, see activation-metrics. For signup optimization, see signup-flow-cro.
docs-agile-integration
lvtd-llc/skills
Integrate documentation work with Agile product development by making docs visible in sprint planning, release trains, definitions of done, review timing, and retrospective improvement. Use when docs are missing from scrum boards, stories, acceptance criteria, release planning, or cross-team work, or when writers need a lightweight process for documentation inside Agile teams.
documentation
w95/awesome-claude-corporate-skills
Write and maintain technical documentation. Trigger with "write docs for", "document this", "create a README", "write a runbook", "onboarding guide", or when the user needs help with any form of technical writing — API docs, architecture docs, or operational runbooks.
agile-ceremonies
89jobrien/steve
Agile ceremonies and sprint management specialist. Use when running standups,
agile-pen
djalmajr/skills
Create and maintain traceable application prototypes exclusively in Pen.dev with auditable prototype-to-code mapping, deterministic official or community shadcn-compatible registry captures, ADS manifests, reusable .pen refs, project-owned DESIGN.md identity, explicit interaction-state frames, functional sections, and paired notes. Use when asked to create or edit a .pen prototype, work in Pen.dev, build a Pen.dev design system, capture components into editable .pen layers, or align product documentation with a .pen artifact before implementation. Do not use for browser-based HTML prototypes; use agile-proto for those.
onboard
mindfold-ai/trellis
Interactive three-part onboarding for new team members to the Trellis AI-assisted workflow system. Covers core philosophy (AI memory, project-specific knowledge, context drift), system structure and command deep-dives, real-world workflow examples, and guideline customization. Use when a new developer joins the project, someone needs to understand the Trellis workflow, or project guidelines need initial setup.
meaningful-linear-issues
stealth-factory/skills
Create complete, analytics-ready Linear issues in ONE pass — resolve the right project (never guess it), and proactively fill the metadata that's technically optional but matters for planning/analytics: priority, estimate, labels (a Type + an Area from the team's existing taxonomy), milestone, assignee, cycle, and relations. Use when asked to 'create/file/open a Linear issue', 'log a ticket', 'add this to Linear', 'make an issue for X', or before any Linear `save_issue` that **creates** an issue or **backfills** missing metadata on a bare one — so the user doesn't have to come back and ask for the labels/estimate/project a second time, and so an issue doesn't land in the wrong project. NOT for routine field edits (status changes, reassignments) — those are also `save_issue` but don't need this.
workshop-facilitation
anotb/management-consulting-plugin
Design and facilitate consulting workshops: strategy offsites, design thinking sessions, innovation sprints, and discovery workshops. Use when planning client-facing facilitated sessions, running stakeholder alignment or prioritization exercises, designing working sessions for strategy development, or building facilitation guides and pre-work. Covers objective-setting, participant planning, methodology selection, agenda design, facilitation technique, and post-workshop follow-through.
wt-land
hoetaek/wt
Use after wt work is reviewed or intentionally discarded, or when the user asks for a wt retrospective: respect workflow policy, pass workflow-linked tasks when needed, merge or prove discard, clean with `wt done`, and record retrospective lessons, timing evidence, action candidates, and harness tuning.
project-manager
igmarin/agnostic-planning-skills
>
fermi-estimation
andurilcode/craftwork
Apply Fermi estimation whenever the user needs a quantitative answer but lacks precise data — or when a number is needed quickly to inform a decision, sanity-check a plan, or evaluate feasibility. Triggers on phrases like "how long will this take?", "how much will this cost?", "is this feasible?", "how many X are there?", "what's the order of magnitude?", "rough estimate?", "ballpark this for me", "how many tokens does this use?", "how does this scale?", or any situation requiring a quantitative judgment under uncertainty. Also trigger to sanity-check existing estimates — a Fermi calculation that disagrees with an official estimate by an order of magnitude is a signal worth investigating. Don't refuse to estimate because you lack data. Decompose and calculate.
agile-metrics
djalmajr/essential-skills
Consolidates objective metrics of a sprint. Use when you need quantitative data about deliveries, blockers, deviations, and velocity to feed retro, sprint review, or capacity decisions.
agile-story
djalmajr/essential-skills
Creates execution plan with tasks for a single story or a localized standalone change. Use when the work fits in one cycle — either a story already scoped by an epic, or a small/localized change that doesn't need decomposition.
agile-roadmap
djalmajr/essential-skills
Maps multi-phase trajectories with dependencies into clear, sequenced roadmaps. Use when work has multiple phases that need sequencing, when decisions today affect future decisions, when stakeholders need to see the whole journey, or when external dependencies exist. Applicable regardless of total duration — a 4-week multi-phase initiative benefits as much as a quarterly roadmap.
ArgocdAppInstall
julianobarbosa/claude-code-skills
Create and manage ArgoCD ApplicationSets for new workloads using the Cafehyna multi-source template pattern. USE WHEN adding a new service to ArgoCD OR creating an ApplicationSet from template OR deploying a new kube-addon OR onboarding a workload to the GitOps platform OR need to know which clusters to target for a service.
agile-iteration-method
joneri/agile-iteration-method
>
plan-sprint
igmarin/agnostic-planning-skills
>
project-sizing-guide
zebbern/claude-code-guide
Software project effort estimation assistant. Outputs three-point estimates (optimistic/most-likely/pessimistic values with confidence intervals), T-shirt sizes, or Function Point Analysis (FPA) counts. Triggered when users ask 'how long will this feature take,' need to assess project workload, perform PERT estimation, T-shirt sizing, FPA, sprint planning, or quote-based effort breakdowns.
scrum-master
aaaaqwq/agi-super-team
Advanced Scrum Master with data-driven team health analysis, velocity forecasting, retrospective insights, and team development expertise. Features comprehensive sprint health scoring, Monte Carlo forecasting, and psychological safety frameworks for high-performing agile teams.
agile-intake
djalmajr/essential-skills
Structures new and vague problems into clear intake documents. Use when the problem is not yet mature enough for the backlog, when someone brings an idea or need without defined scope, or when you need to decide what the next artifact in the flow should be.
agile-refinement
djalmajr/essential-skills
Validates planning artifacts and reviews code for quality, consistency, and completeness. Use to lint planning documents (cross-references, dependencies, format) or to review changed code (security, coherence, scope, quality).
agile-retro
djalmajr/essential-skills
Conducts retrospective with learnings and improvement actions. Use when a cycle, sprint, or delivery has ended and the team needs to reflect on what worked and what needs to change. Also absorbs post-implementation reflection aspects.
agile-epic
djalmajr/essential-skills
Structures large initiatives into a decomposed backlog with roadmap, dependencies, and verification. Generates an overview file plus individual story files with tasks. Use when work requires several coordinated stories, has dependencies between deliveries, or needs a roadmap.
onboardingV2
launchdarkly/experimental-agent-skills
Scripted, branded onboarding for LaunchDarkly. Fixed sequence with LaunchDarkly voice and tone. Enforces step completion before advancing. Redirects drift. Use when the user wants to set up LaunchDarkly from scratch or asks to start onboarding.
agile-status
djalmajr/essential-skills
Tracks delivery progress in three modes — checkpoint (daily), consolidation (period report), and closure (post-implementation). Use when you need to record progress, consolidate a period, or formally close a delivery.
agile-review
djalmajr/essential-skills
Prepares sprint review and demo of deliveries for stakeholders. Use when the sprint has ended and it is necessary to present what was delivered, what changed in scope, what is pending, and what decisions are needed.
codex-retrospective
majiayu000/spellbook
Use when you want Codex to review its own recent history (last N days or specific period) and improve its behavior. Produces minimal, high-signal updates to AGENTS.md and tiny reusable skills. The goal is long-term fluency — Codex gradually becomes better at your specific style, constraints, and workflows.
fp-brief
sd0xdev/sd0x-harness
First-principles briefing from technical documents. Use when: understanding why decisions were made, onboarding to feature reasoning, reviewing decision chains, explaining doc from first principles. Not for: PM/CTO summary (use project-brief), pre-doc analysis (use feasibility-study), code explanation (use codex-explain). Output: structured reasoning chain with sensitivity analysis.
sprint-planner
jkappers/agent-skills
>
plan-sprint
pjt222/agent-almanac
>
project-planner
amanning3390/hermeshub
Project planning — break down tasks, estimate timelines, track progress, manage dependencies. Use when the user mentions project planning, task breakdown, roadmap, sprint planning, or milestone tracking.
manage-backlog
pjt222/agent-almanac
>
agile-onboarding
djalmajr/essential-skills
Onboarding guide for new team members in the agile flow with AI. Use when someone new joins the team and needs to understand how the planning, execution, and tracking flow works with AI agents.
meeting-facilitator
tatat/agents-playground
Plan and structure effective meetings with agendas and follow-ups
bmad-retrospective
bmad-labs/skills
Post-epic review to extract lessons and assess success. Use when the user says "run a retrospective" or "lets retro the epic [epic]"
bmad-sprint-planning
bmad-labs/skills
Generate sprint status tracking from epics. Use when the user says "run sprint planning" or "generate sprint plan"
skillsman-readme
yatmn/skillsman
Create or update project README documentation for software repositories. Use when asked to write, rewrite, audit, refresh, sync, or update README.md, README.zh-CN.md, project onboarding docs, quick-start docs, or bilingual English-first README files; especially when Codex must inspect a repository, infer real setup/dev/test/deploy commands, update docs after code changes, and produce or maintain an English primary README with a linked Chinese companion.
agile-sprint
djalmajr/essential-skills
Plans sprint by selecting items from backlog, defining objective, capacity, and execution order. Use at the beginning of a work cycle to align what will be done.
agile-router
djalmajr/essential-skills
Routes to the appropriate agile skill based on context. Use when you need guidance on which skill to use — whether for planning, ceremonies, or tracking.
mapping-suite
nickcrew/claude-cortex
User-triggered orchestrator that walks the user through running multiple sibling mapping/audit/doc skills against a shared scope, then assembles their outputs into one navigable artifact. Coaches rather than auto-runs — at each step the orchestrator presents the next sibling skill, recommended scope inheritance, and approval gate; the user invokes the sibling and confirms before moving on. Resolves the prior arch-analysis lookup once at suite start so every sibling skill inherits the same scope. Records each run's output path in a suite manifest. Produces a combined navigation HTML that links to each sibling's standalone HTML for one-stop sharing. Ships two named recipes — "release-driver onboarding" (for tooling that drives releases) and "deployed-system onboarding" (for systems that get deployed) — and supports custom plans. Trigger on "run our mapping suite," "do a complete onboarding," "build the combined report," "I need to onboard to system X," "give me the full picture of this codebase," or when the user names two-or-more sibling analyses to coordinate. Not for running a single sibling skill in isolation (invoke it directly), and not for bypassing approval gates (this skill coaches, never autoruns).
effort-estimator
flpbalada/fb-skills
Estimate engineering effort from scope, risk, unknowns, and verification cost. Use when sizing features, splitting work, planning sprints, comparing implementation options, or deciding whether a task is XS through XL, provided enough task detail exists for a rough estimate; avoid for product value, requirements quality, or business-case analysis.
onboarding-cro
silvainfm/claude-skills
When the user wants to optimize post-signup onboarding, user activation, first-run experience, or time-to-value. Also use when the user mentions "onboarding flow," "activation rate," "user activation," "first-run experience," "empty states," "onboarding checklist," "aha moment," or "new user experience." For signup/registration optimization, see signup-flow-cro. For ongoing email sequences, see email-sequence.
design-workshop-facilitation
slb2248/ai-ux-skills
Facilitate effective design workshops for problem-solving, ideation, customer journey mapping, and team alignment.
opensource-guide-coach
xixu-me/skills
Use when a user wants guidance on starting, contributing to, growing, governing, funding, securing, or sustaining an open source project, or asks about contributor onboarding, community health, maintainer burnout, code of conduct, metrics, legal basics, or open source project adoption.