bad_requires_token

Validate requires tokens in SKILL.md frontmatter and reject malformed entries.

40|6|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/0xmariowu/Autosearch --skill bad-requires-token
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bad_requires_token
Source: https://github.com/0xmariowu/Autosearch/tree/main/tests/fixtures/skills/bad_requires_token
Command: npx skills add https://github.com/0xmariowu/Autosearch --skill bad-requires-token

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures Skill definitions are well-formed by validating 'requires' tokens in the YAML frontmatter and rejecting any entries that are malformed to prevent loader failures.

Core Features & Use Cases

  • Detect malformed requires entries in SKILL.md frontmatter and report precise validation errors.
  • Integrate with a skill loader to fail fast during onboarding of new skills.
  • Use case: when adding a new skill, automatically verify metadata consistency before activation.

Quick Start

Run the loader on a Skill unit to identify and reject malformed requires tokens.

Frequently Asked Questions about bad_requires_token

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

FAQPage Schema
How do I validate requires tokens in YAML frontmatter?

To validate requires tokens in YAML frontmatter, run a skill loader that enforces schema checks on skill definitions to detect malformed entries and report precise validation errors before activation.

Why does the skill loader fail on malformed requires tokens?

The skill loader fails because malformed requires tokens in SKILL.md frontmatter violate metadata consistency. This validation mechanism enforces schema checks for fields like name and description to prevent processing invalid definitions.

What is the best way to check skill manifests for invalid frontmatter fields?

The best way to check skill manifests for invalid frontmatter fields is to run a validation check that rejects skill definitions with malformed requires tokens, ensuring only properly formatted entries pass during the onboarding workflow.

Can I integrate frontmatter validation into an automated skill loading workflow?

Yes, you can integrate frontmatter validation into a skill loading workflow to fail fast during the onboarding of new skills, automatically verifying metadata consistency and rejecting invalid requires tokens.

Do I need dependencies to run validation on skill definitions?

No dependencies are required to run validation on skill definitions. The validation operates directly on the SKILL.md frontmatter to enforce schema checks and reject malformed requires tokens without external libraries.