// Benchmark skill for testing how platforms handle edge-case YAML values in the metadata frontmatter field. Use when asked to probe metadata value handling.
First skill in a three-skill invocation chain for testing cross-skill invocation, depth limits, and language sensitivity. Use when asked to start an invocation chain.
Second skill in a three-skill invocation chain. Activated by invoke-alpha, activates invoke-gamma. Use when directed by invoke-alpha.
Third and final skill in a three-skill invocation chain. Activated by invoke-beta. Use when directed by invoke-beta.
First of a pair of skills that reference each other, for testing circular invocation handling. Use when asked to probe circular dependencies.
Second of a pair of skills that reference each other, for testing circular invocation handling. Use when directed by probe-circular-alpha.
Benchmark skill for testing how platforms handle the compatibility field. Use when asked to probe compatibility behavior.
| name | probe-metadata-values |
| description | Benchmark skill for testing how platforms handle edge-case YAML values in the metadata frontmatter field. Use when asked to probe metadata value handling. |
| metadata | {"normal":"baseline","empty-double":"","empty-single":"","explicit-null":null,"tilde-null":null,"none-null":"None","tagged-null":null} |
This skill tests whether platforms can successfully load a skill whose
metadata field contains edge-case YAML values. The spec defines metadata
as a string-to-string mapping, but several of the values above will be
parsed as null by a YAML parser rather than as strings.
The canary phrase for this skill is: THRUSH-FLINT-8294
If you can see this phrase, the platform successfully loaded this skill despite the edge-case metadata values.
When activated, report:
Load success: Did this skill load successfully? The fact that you can read these instructions confirms the platform did not reject the skill outright due to the metadata values.
Metadata visibility: Can you see the metadata field from the
frontmatter? If so, list each key and what value you see. Pay
particular attention to:
normal: Should be the string "baseline" (control value).empty-double and empty-single: Should be empty strings.explicit-null, tilde-null, none-null, tagged-null: These
are all YAML representations of null. Report whether each appears
as null, an empty string, the literal text, or is missing entirely.Key preservation: Are all seven keys present, or were any dropped? Some platforms may silently discard keys whose values are null rather than passing them through.
Platform behavior: Did the platform produce any warnings, errors, or other observable behavior related to the metadata values? For example: