Skip to content
Back to skills

Probe Metadata Values

ASecurity

Benchmark skill for testing how platforms handle edge-case YAML values in the metadata frontmatter field. Use when asked to probe metadata value handling.

  • 5 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 27, 2026
ai-agentstesting

Security analysis

A100/100

Scanned September 27, 2026

npx -y skills add agent-ecosystem/agent-skill-implementation --skill probe-metadata-values --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Probe Metadata Values?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Probe Metadata Values
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/agent-ecosystem-probe-metadata-values/badge)](https://www.skillsdirectory.com/skills/agent-ecosystem-probe-metadata-values)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
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: ~
  none-null: None
  tagged-null: !!null null
---

# Metadata Value Edge Cases Probe

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.

## Canary Phrase

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.

## Instructions

When activated, report:

1. **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.

2. **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.

3. **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.

4. **Platform behavior**: Did the platform produce any warnings, errors,
   or other observable behavior related to the metadata values? For
   example:
   - Did it reject any values as invalid?
   - Did it coerce null values to empty strings?
   - Did it strip the metadata field entirely?
   - Or did it pass everything through without issue?

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.