valid-skill

Constructs a reusable, secure, and customizable text generation engineuze.

Updated Jan 10, 2026
One-click install
npx skills add https://github.com/0xHoneyJar/rm-lurker --skill valid-skill-0xhoneyjar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: valid-skill
Source: https://github.com/0xHoneyJar/rm-lurker/tree/main/tests/fixtures/registry/skills/test-vendor/valid-skill
Command: npx skills add https://github.com/0xHoneyJar/rm-lurker --skill valid-skill-0xhoneyjar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill validates license metadata during loader tests to ensure only compliant licenses are accepted and to catch missing or invalid license declarations early.

Core Features & Use Cases

  • License validation: checks that license fields in SKILL.md and index.yaml meet expected structure and content.
  • Test fixture verification: confirms that test fixtures declare correct name, vendor, and license metadata for unit tests.
  • Use Case: Used in test_constructs_loader.bats to verify correct handling of valid licenses during skill loading.

Quick Start

Run the unit tests that exercise license validation logic against the fixture, e.g., execute the repository's license-validation tests.

Frequently Asked Questions about valid-skill

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

FAQPage Schema
How do I validate license metadata in test fixtures?

You can validate license metadata by running unit tests that check SKILL.md and index.yaml fields to ensure only compliant licenses are accepted during loader tests. This catches missing or invalid license declarations early in testing workflows.

What does license validation check in SKILL.md and index.yaml?

License validation checks that the license fields in SKILL.md and index.yaml meet expected structure and content. It verifies that defined name, description, and license tags are present and correctly formatted for test fixtures.

Do I need external dependencies to run license validation tests?

No external dependencies are required for license validation tests. The validation relies solely on the repository's test fixtures, exercising the skill registry and license handling without needing additional packages or tools.

How do I verify test fixtures declare correct license metadata for unit tests?

Test fixture verification confirms that test fixtures declare correct name, vendor, and license metadata for unit tests. Execute the repository's license-validation tests to verify correct handling of valid licenses during skill loading.

When do I need license validation in unit-testing workflows?

License validation is needed in unit-testing workflows when exercising the skill registry and license handling, especially when loading test fixtures. It ensures only compliant licenses are accepted and catches invalid declarations early.