test-skill

Validate per-client skill manifests for Cursor-like environments.

376|31|Updated Jan 30, 2026
One-click install
npx skills add https://github.com/avifenesh/agnix --skill test-skill-avifenesh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-skill
Source: https://github.com/avifenesh/agnix/tree/main/tests/fixtures/per_client_skills/.cursor/skills/test-skill
Command: npx skills add https://github.com/avifenesh/agnix --skill test-skill-avifenesh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps ensure per-client skill configurations are compliant with Cursor-like tooling rules, catching disallowed fields before deployment.

Core Features & Use Cases

  • Validate manifests to detect fields not supported in specific runtimes (e.g., model, context, agent).
  • Cross-environment portability checks to ensure consistent behavior across clients and tooling.
  • Use Case: As a QA step, run this skill against a sample manifest to verify that CR-SK-001 and XP-SK-001 rules are triggered for invalid fields.

Quick Start

Run a test with a sample manifest to verify that CR-SK-001 and XP-SK-001 rules fire for disallowed fields.

Frequently Asked Questions about test-skill

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

FAQPage Schema
How do I validate a per-client skill manifest for unsupported runtime fields?

Per-client skill manifest validation checks configuration files against runtime tooling constraints. It identifies disallowed fields such as model, context, and agent to prevent integration pipeline errors and ensure cross-environment portability.

What are the CR-SK-001 and XP-SK-001 checks in skill manifest validation?

CR-SK-001 and XP-SK-001 are specific rule-checks triggered during skill manifest validation. They fire when disallowed fields like model, context, or agent are detected, ensuring the manifest meets required compliance standards.

How do I test my skill manifest to ensure it triggers the right validation errors?

Run a test with a sample manifest to verify that CR-SK-001 and XP-SK-001 rules fire for disallowed fields. This QA step confirms that invalid fields like model, context, and agent are properly caught before deployment.

Does my skill configuration need to pass portability checks for different client environments?

Yes, cross-environment portability checks are necessary to ensure consistent behavior across clients. Validating per-client skill manifests confirms that configurations do not contain unsupported fields that break tooling compatibility.

Why are model, context, and agent fields considered disallowed in certain skill manifests?

Model, context, and agent fields are disallowed because they are not supported in specific Cursor-like runtime environments. Including them violates CR-SK-001 and XP-SK-001 rules, leading to validation failures and deployment blocks.