Afegits recentment
Els últims skills afegits al catàleg. Descobreix les novetats!
competitive-analysis-process
HMS091
"Orchestrate a complete competitive analysis across six steps, from landscape to strategic direction. Use when you need the full picture, not a single scan or card."
company-research
HMS091
Create a company research brief with executive quotes, product strategy, and org context. Use when preparing for interviews, competitive analysis, partnerships, or market-entry work.
company-intel
HMS091
Research a company, industry, or competitor set using web search and seven analytical lenses. Use when you need structured intel that feeds downstream PM skills.
business-health-diagnostic
HMS091
Diagnose SaaS business health across growth, retention, efficiency, and capital. Use when preparing a business review or prioritizing urgent fixes.
battle-card-builder
HMS091
"Research and draft a competitive battle card from public evidence — every claim labeled and sourced. Use when a rep needs a field-action card, not a research report."
ansoff-matrix
HMS091
"Map evidence-backed growth options across the Ansoff Matrix with risk-rated sequencing. Use when the question is where the next tranche of growth comes from, and at what risk."
altitude-horizon-framework
HMS091
Understand the PM-to-Director transition through altitude and horizon thinking. Use when diagnosing scope, time-horizon, or leadership-level gaps.
ai-shaped-readiness-advisor
HMS091
Assess whether your product work is AI-first or AI-shaped. Use when evaluating AI maturity and choosing the next team capability to build.
agent-orchestration-advisor
HMS091
Design multi-agent AI workflows with clear boundaries, handoffs, and monitoring. Use when a complex PM task should run as parallel specialized agents instead of one linear process.
acquisition-channel-advisor
HMS091
Evaluate acquisition channels using unit economics, customer quality, and scalability. Use when deciding whether to scale, test, or kill a growth channel.
writing-plans
HMS091
"Write implementation plans: bite-sized tasks, paths, code."
windows-github-upgrade
HMS091
Upgrade Windows portable software from GitHub releases — proxy detection, download, and safe replacement.
github-repo-management
HMS091
"Clone/create/fork repos; manage remotes, releases."
github-pr-workflow
HMS091
"GitHub PR lifecycle: branch, commit, open, CI, merge."
github-issues
HMS091
"Create, triage, label, assign GitHub issues via gh or REST."
github-issue-to-pr
HMS091
"Carry a GitHub issue to a verified PR with honest CI state."
github-code-review
HMS091
"Review PRs: diffs, inline comments via gh or REST."
github-auth
HMS091
"GitHub auth setup: HTTPS tokens, SSH keys, gh CLI login."
decoupler
scverse
Read before any task that mentions decoupler, one of its bundled example datasets, or asks which transcription factors (TFs), pathways, or gene sets are most active, enriched, up or down in expression data - bulk RNA-seq treated vs control, single-cell cell types or clusters, condition contrasts across donors (pseudobulk), spatial transcriptomics regions or niches, and pseudotime or differentiation trajectories - with the exact 2.x workflow (dc.op networks, dc.pp preprocessing, dc.mt scoring, dc.tl ranking) that reproduces the documented results. Also covers decoupler's networks (CollecTRI, PROGENy, DoRothEA, MSigDB), supported organisms/species and ortholog translation, resource licenses, and the conventions for plotting or visualizing its results. Also read for conceptual, best-practice or multiple-choice questions about how an agent should work with decoupler.
Skill review: the default rubric
usirin
added.
writing-plans
Viqto0r
Use when a task is large enough to need more than one or two tool calls — a multi-file change, a new feature, a refactor. Breaks the work into small ordered steps with exact paths and a verification for each.
verification-before-completion
Viqto0r
Use BEFORE declaring a task done or reporting success — a feature, a bug fix, a file you generated. Forces you to run the verification you promised instead of trusting that the code looks right.
test-driven-development
Viqto0r
Use when writing or changing behaviour that can be tested — a bug fix, a new function, a parser, a formatter. Write the failing test first, watch it fail, then make it pass. Prevents tests that only pass because they were written against the finished code.
systematic-debugging
Viqto0r
Use when something is broken and the cause is not obvious — a failing test, a wrong result, a hang, a crash. Four phases: reproduce, isolate, hypothesize, fix. Prevents guessing.