artifact.validate.types

Validate artifact type names against the Betty Framework registry and return metadata with fuzzy-match alternatives.

2|Updated Oct 22, 2025
One-click install
npx skills add https://github.com/epieczko/betty --skill artifact-validate-types
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: artifact.validate.types
Source: https://github.com/epieczko/betty/tree/main/skills/artifact.validate.types
Command: npx skills add https://github.com/epieczko/betty --skill artifact-validate-types

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validates artifact type names against the Betty registry and returns metadata with suggestions for invalid types.

Core Features & Use Cases

  • Checks existence in registry
  • Returns file_pattern, content_type, schema
  • Provides singular/plural and fuzzy-match suggestions

Quick Start

python artifact_validate_types.py --artifact_types '["threat-model"]'

Frequently Asked Questions about artifact.validate.types

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

FAQPage Schema
How do I validate artifact type names against a registry?

Artifact type validation checks if your type names exist in the Betty Framework registry and returns complete metadata including file patterns, content types, and schemas. Run the validator with your artifact types to confirm they're recognized and retrieve their configurations.

What should I do when an artifact type name doesn't match the registry?

The validator provides fuzzy-matching suggestions for invalid types, including singular/plural variants, generic vs specific forms, and close spellings. Review suggestions to find the correct registered type name or verify the spelling matches registry expectations.

Can I verify that schema files exist for my artifact types?

Yes. Enable the check_schemas parameter to verify schema files exist alongside type validation. The validator returns warnings if referenced schemas are missing, helping catch configuration gaps early in the workflow.

How do I get metadata for valid artifact types?

Validated artifact types return complete metadata from the registry including file_pattern, content_type, and schema location. The output distinguishes valid types from invalid ones and provides all associated registry information in a single pass.

When should I run artifact type validation in my workflow?

Apply validation during skill creation to detect invalid types before deployment. Running it early catches naming errors and configuration issues, preventing downstream failures and ensuring all referenced schemas and patterns are correct.