Skills › Engineering › Dependency Research

Dependency Research

Research a library or package before adding it — downloads, maintenance status, known issues, and alternatives.

Superpowers: handler_research · handler_monitor · handler_generate

When to use: You're evaluating a new dependency and want to make an informed decision before adding it to the codebase.

Steps

Get an overview of the package

Superpower: handler_research — live API reference →

POST /v2/superpowers/handler_research
{
  "task": "answer",
  "query": "What is [package-name]? Is it actively maintained? What are known issues or limitations?"
}

Replace [package-name] with the npm/pip/cargo package you're evaluating.

Check recent community discussions and issues

Superpower: handler_monitor — live API reference →

POST /v2/superpowers/handler_monitor
{
  "task": "reddit",
  "query": "[package-name] issues bugs security vulnerability 2026",
  "days": 180
}

Produce a dependency evaluation report

Superpower: handler_generate — live API reference →

POST /v2/superpowers/handler_generate
{
  "task": "chat",
  "prompt": "Write a dependency evaluation report for [package-name]. Sections: (1) What it does and why it's useful, (2) Maintenance health (last release, open issues, bus factor), (3) Known issues or limitations, (4) Community trust signals, (5) Alternatives to consider, (6) Recommendation: add / add with caution / avoid. Data: [steps 1-2]"
}

From previous step: research (step 1) + community discussions (step 2) → inject

Outcome: Dependency evaluation: maintenance health, known issues, alternatives, and a clear add/avoid recommendation.

Fetch this skill via API

GET /v2/skills/dependency-research
Authorization: Bearer sk-hndlr-...