discover-dependency

Enumerate build subproblems and classify external resources as libraries, assets, services, or bespoke logic.

Updated May 21, 2026
One-click install
npx skills add https://github.com/mica-agent/mica-solar-system --skill discover-dependency
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: discover-dependency
Source: https://github.com/mica-agent/mica-solar-system/tree/main/.qwen/skills/discover-dependency
Command: npx skills add https://github.com/mica-agent/mica-solar-system --skill discover-dependency

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents brittle, runtime-breaking agent builds by forcing you to discover, classify, and verify external libraries, assets, and services before implementation.

Core Features & Use Cases

  • Dependency enumeration and classification: Breaks the build into subproblems and labels each as library, asset, service, or bespoke.
  • Recall-first decision workflow: Uses what you already know as the first pass, then verifies with targeted checks instead of broad search.
  • Safe URL verification discipline: Ensures any URL you plan to use is validated via inspection tools to avoid CORS failures and 404s.
  • Budget-controlled external search: Limits web search iterations per subproblem and escalates to fallbacks or user input after the cap.
  • Multi-kind builds supported: Handles the common case where a single card needs multiple dependency types (e.g., Three.js + textures + an API).

Quick Start

Use discover-dependency to plan the external resources for a new interactive card (for example, a Three.js visualization) before writing or selecting any code, ensuring every library/asset/service is verified and documented.

Frequently Asked Questions about discover-dependency

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

FAQPage Schema
How do I verify external dependencies before building an interactive component?

To verify external dependencies before building, you enumerate build subproblems and classify each as a library, asset, service, or bespoke logic, then validate URLs via inspection to prevent CORS failures and runtime breaks.

What is the best way to prevent CORS failures and 404 errors when loading external libraries?

Preventing CORS failures and 404s requires a recall-first verification workflow that enforces URL inspection before committing, checking CORS/UMD configurations and endpoint shapes to ensure external resources load reliably.

How do I classify and validate multiple dependency types like Three.js libraries and texture assets?

Classifying and validating multiple dependency types involves breaking the build into subproblems, labeling each dependency kind, and applying targeted checks to verify libraries, downloadable assets, and runtime API calls together.

Does this dependency discovery workflow support runtime API calls and downloadable model files?

Yes, the dependency discovery workflow supports runtime API calls and downloadable files like textures or models by validating endpoint shapes and URLs, ensuring both services and assets are verified before implementation.

When should I use a recall-first verification workflow instead of broad web searches for dependencies?

A recall-first verification workflow should be used when you need budget-controlled dependency discovery, using existing knowledge as a first pass and escalating to targeted URL inspection or user input only after search caps are reached.

Why does my interactive card break at runtime when loading external JavaScript resources?

Interactive cards break at runtime when external JavaScript resources are unverified, causing CORS or 404 failures; using a dependency decisions table to document and validate URLs beforehand prevents these brittle builds.