القائمة
this file triggers a yaml parse error
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Perform a fallback role by existing only in the alternate search path. Tests use this to assert that discovery walks every search path, not just the first one, when resolving names that do not appear in the primary path.
Perform the same role as the primary valid-skill fixture but live in an alternate search path so tests can assert precedence rules (first search path wins). The body text here is different from the primary fixture so a test can tell which copy was loaded.
A skill with a non-kebab-case name. The validator should reject this because the name format is used as an identifier across search paths and registries.
A skill whose body is empty. The tolerant validator should reject this since the body carries the actual instructions the orchestrator needs.
Perform strict-mode checks on a skill whose body omits the When NOT to Use section. Everything else about the body is fine, the description is long enough, opens with an action verb, and includes a Not for anti-trigger. The one failure this fixture isolates is the missing When-NOT-to-Use heading which is the single most commonly skipped authoring convention.
Perform strict-mode checks against a skill that has plenty of content but no anti-trigger clause. This description is deliberately padded to cross the 300-character lower bound while leaving the Not-for segment absent so the validator focuses solely on the missing anti-trigger rule. It includes use-when triggers and enough substance to look convincing at first glance.
| name | malformed-yaml stray indented line that is not under a preceding key |
| description | this file triggers a yaml parse error |
Body text the parser never reaches.
