registry-dep-skill

Provide a minimal versioned registry dependency for Skillset smoke tests.

111|9|Updated Jan 6, 2026
One-click install
npx skills add https://github.com/Peiiii/skild --skill registry-dep-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: registry-dep-skill
Source: https://github.com/Peiiii/skild/tree/main/examples/registry-dep-skill
Command: npx skills add https://github.com/Peiiii/skild --skill registry-dep-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It provides a ready-to-use registry dependency that can be included by larger Skillsets to test integration and dependency resolution.

Core Features & Use Cases

  • Dependency for Skillsets: acts as a mock or placeholder skill that other skills depend on during testing.
  • Lightweight and versioned: versioned in frontmatter and published to a local/dev registry for integration tests.

Quick Start

Add registry-dep-skill to your Skillset dependencies to run smoke tests in your local registry.

Frequently Asked Questions about registry-dep-skill

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

FAQPage Schema
How do I mock a registry dependency for Skillset testing?

To mock a registry dependency for Skillset testing, you can include a lightweight, versioned placeholder skill in your local or dev registry to provide deterministic test results during integration checks.

What is a registry dependency in a Skillset smoke test?

A registry dependency in a Skillset smoke test is a minimal, versioned mock skill that acts as a placeholder, allowing larger Skillsets to verify integration and dependency resolution in a local dev registry.

How do I test Skillset dependency resolution in a local registry?

You test Skillset dependency resolution by adding a minimal mock skill to your local registry dependencies, which serves as a predictable reference to validate that integration and dependency resolution work correctly.

Do I need a versioned skill to run integration tests in a dev registry?

Yes, using a versioned skill is necessary for dev registry integration tests because it provides a deterministic reference point for dependency resolution, ensuring predictable smoke test results.

Can I use a placeholder skill for local registry integration checks?

Yes, you can use a placeholder skill for local registry integration checks, as it functions as a ready-to-use mock dependency that enables larger Skillsets to test dependency resolution without complex setup.

Why does my Skillset smoke test fail during dependency resolution?

A Skillset smoke test fails during dependency resolution when required registry dependencies are missing, which can be fixed by adding a minimal, deterministic mock skill to your local registry dependencies.