opportunity-scanner

Scan code repositories, package ecosystems, and security advisories for upgrade opportunities.

Updated Mar 24, 2026
One-click install
npx skills add https://github.com/Heretek-AI/heretek-skills --skill opportunity-scanner-heretek-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: opportunity-scanner
Source: https://github.com/Heretek-AI/heretek-skills/tree/main/skills/opportunity-scanner
Command: npx skills add https://github.com/Heretek-AI/heretek-skills --skill opportunity-scanner-heretek-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, npm, jq, clawhub.

What problem does it solve?

Identify and surface external opportunity signals from code repositories, package ecosystems, and security advisories to guide proactive planning.

Core Features & Use Cases

  • Automated aggregation of opportunities from upstream releases, npm updates, and new skills in ClawHub.
  • Quick checks for security advisories and release opportunities to inform roadmap decisions.
  • Use Case: For a release cycle, run scans to surface upgrade opportunities and potential security fixes.

Quick Start

Run the opportunity-scanner.sh script with the --scan flag to perform a full scan of all sources.

Frequently Asked Questions about opportunity-scanner

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I scan for npm updates and security advisories across multiple repositories?

You can scan for npm updates and security advisories by running a shell-based scanning workflow with the --scan flag. It aggregates upstream releases and security advisories across multi-repo environments to surface external opportunity signals.

What is the best way to surface external opportunity signals for release readiness checks?

Surfacing external opportunity signals for release readiness is best handled by automated aggregation of upstream releases, npm updates, and security advisories. This workflow informs roadmap decisions by identifying potential upgrade opportunities and security fixes.

Does the opportunity scanning workflow require specific environment configuration to run?

Yes, the opportunity scanning workflow reads environment configuration before executing. You need git, npm, jq, and clawhub installed in your environment to support the shell-based scanning process and structured JSON output.

Can I get structured JSON output from scanning upstream releases for programmatic consumption?

Yes, you can get structured JSON output from scanning upstream releases by running the workflow with the --json mode. This optional mode formats the aggregated npm updates and advisory results for programmatic consumption.

How do security advisories factor into roadmap planning during a release cycle?

Security advisories factor into roadmap planning by highlighting potential security fixes during a release cycle. Running scans surfaces these advisories alongside upstream release opportunities to guide proactive planning and release readiness checks.