Skip to main content

Overview

Skill validation ensures that skills are properly defined, secure, and ready for production use. FastSkill provides multiple levels of validation to catch issues early in the development process.
Validation happens at multiple stages: definition validation, registration validation, and runtime validation.

Validation Types

1. Structure Validation

Validates that skill definitions follow the correct schema and format:

2. Security Validation

Checks for potential security issues in skill definitions:

3. Quality Validation

Ensures skills meet quality standards:

Validation Rules

Required Fields

string
required
  • Must be unique within the service
  • Alphanumeric characters, dashes, and underscores only
  • 3-50 characters in length
  • Cannot start or end with dashes/underscores
string
required
  • Human-readable name
  • 1-100 characters in length
  • No special formatting requirements
string
required
  • Detailed description of functionality
  • 10-500 characters in length
  • Should explain what the skill does
string
required
  • Semantic version format (e.g., “1.0.0”)
  • Follows MAJOR.MINOR.PATCH convention
  • Should be updated for breaking changes

Optional Fields Validation

string
  • Comma-separated list of tags
  • Each tag 2-30 characters
  • Alphanumeric, dashes, and underscores only
  • Maximum 20 tags
string
  • Comma-separated list of capabilities
  • Each capability 3-50 characters
  • Descriptive of actual functionality
  • Maximum 20 capabilities
string
  • Path relative to skill storage directory
  • Must exist and be readable
  • Should be a Python file or markdown document
integer
  • 1-300 seconds
  • Must be reasonable for the skill’s operations
integer
  • 32-2048 MB
  • Must be sufficient for skill execution

Validation CLI

Use the CLI for validation workflows:

Validation Output

Custom Validation

Create custom validation rules for your organization:

Batch Validation

Validate multiple skills efficiently:

Validation Webhooks

Set up webhooks for validation events:

Integration with CI/CD

GitHub Actions

Pre-commit Hooks

Best Practices

1

Validate early and often

Run validation as part of your development workflow, not just before deployment.
2

Use multiple validation levels

Combine structure, security, and quality validation for comprehensive coverage.
3

Set up automated validation

Integrate validation into your CI/CD pipeline to catch issues before they reach production.
4

Monitor validation metrics

Track validation success rates and common issues to improve skill quality over time.
5

Document validation rules

Maintain clear documentation of your validation rules and requirements for skill contributors.

Troubleshooting

Missing required fields: Ensure all required fields are present and have valid values.
Invalid field types: Check that field values match expected types (string, integer, boolean, etc.).
Common security issues: Review skill dependencies, execution permissions, and network access requirements.
Optimize validation: Use validation caching for repeated checks during development.
Effective validation catches issues early and ensures skills meet quality standards. Invest time in setting up comprehensive validation for your skill ecosystem.