Agent skill
markdown-version-extractor
Extracts 'version' or 'uuid' fields from YAML frontmatter using uv.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/data/markdown-version-extractor
SKILL.md
Markdown Version Extractor
Use this skill to identify the version or UUID of a skill or project stored in Markdown frontmatter. This is a critical dependency for the Version Sync phase of the Persona Protocol.
Capabilities
- Parses YAML frontmatter using the
python-frontmatterlibrary. - Safely extracts versioning identifiers (
uuidorversion). - Provides available metadata keys if the specific version tag is missing.
Execution Logic
The agent MUST use uv run and MUST provide absolute paths for both the script and the target file.
Command Template:
uv run <absolute_path_to_get_version.py> "<absolute_path_to_target_md_file>"
Guidance for the Agent
- NO DIRECT PYTHON: You are FORBIDDEN from calling
pythonorpython3directly. This script uses PEP 723 inline dependencies that require theuvruntime. - Absolute Paths: You must resolve the current working directory to provide the full absolute path for:
- The script itself.
- The file being checked.
- Version Identifier Priority:
- The Registry uses the
uuidfield. - Local files may use either
versionoruuid. - If the script returns a
uuid, use that for comparison against the registry'suuid.
- The Registry uses the
- Error Handling:
- If the output shows
status: "missing_tag", check themetadata_keysin the JSON. If neitheruuidnorversionexists, consider the skill unversioned and trigger an update. - If the file is missing or not Markdown, report a failure.
- If the output shows
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?