SkillAgentSearch skills...

frontmatter-parsing

YAML frontmatter parsing and manipulation for .planning/ documents. Provides read, write, update, query, and validation operations on frontmatter blocks in GSD markdown artifacts.

Install / Use

npx skills add a5c-ai/babysitter --skill frontmatter-parsing

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

92/100

Category

Automation

Supported Platforms

Universal

Our assessment of frontmatter-parsing

frontmatter-parsing scores 92/100 on our quality scale, 873rd of 2,790 Automation skills we index (top 32%).

Its SKILL.md is 7.0 KB long, well organised into 23 sections with 10 code examples: a thorough specification that gives an agent plenty to work with.

With 1,809 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
29/30
Structure
20/20
Description
15/15
Adoption
14/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so frontmatter-parsing is actively maintained.
  • Our last check on 2026-10-27 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-09-30. Automated pattern scan on 2026-09-30. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

frontmatter-parsing compared with similar skills

All 4 of these similar skills score higher than frontmatter-parsing; compare them before choosing.

SkillScoreStarsUpdatedFormat
frontmatter-parsing (this skill)by a5c-ai921.8k2mo agoSKILL.md
Agent-Reachby Panniantong100112.3k8d agoCLAUDE.md
rufloby ruvnet10081.9ktodayCLAUDE.md
Claude-Code-Game-Studiosby Donchitos10039.7k7d agoCLAUDE.md
Scraplingby D4Vinci100103.6k2d agoMCP Server

Frequently asked questions

How do I install frontmatter-parsing?
Run npx skills add a5c-ai/babysitter --skill frontmatter-parsing. The install tabs above show the steps for each supported agent.
Which AI agents does frontmatter-parsing work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is frontmatter-parsing safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is frontmatter-parsing still maintained?
The repository was last updated about 2 months ago, so frontmatter-parsing is actively maintained.

name: frontmatter-parsing description: YAML frontmatter parsing and manipulation for .planning/ documents. Provides read, write, update, query, and validation operations on frontmatter blocks in GSD markdown artifacts. allowed-tools: Read Write Edit Glob Grep metadata: author: babysitter-sdk version: "1.0.0" category: gsd-core backlog-id: SK-GSD-005 graph: domains: [domain:software-engineering] skillAreas: [skill-area:agentic-loops, skill-area:orchestration-loop] workflows: [workflow:feature-development] topics: [topic:developer-experience] roles: [role:tech-lead, role:backend-engineer]

status: in-progress phase: 72 wave: 1 depends_on: [] files_modified: ["src/auth/oauth.ts", "src/auth/tokens.ts"] created: 2026-03-02 updated: 2026-03-02

Plan content below...


## Capabilities

### 1. Parse Frontmatter

Extract frontmatter from a markdown file into structured data:

```yaml
# Input file: .planning/phase-72/PLAN-1.md
---
status: planned
phase: 72
plan_number: 1
wave: 1
depends_on: []
files_modified:
  - src/auth/oauth.ts
  - src/auth/tokens.ts
  - src/middleware/auth.ts
task_count: 4
created: 2026-03-02
gap_closure: false
---

Parsed result:

{
  "status": "planned",
  "phase": 72,
  "plan_number": 1,
  "wave": 1,
  "depends_on": [],
  "files_modified": ["src/auth/oauth.ts", "src/auth/tokens.ts", "src/middleware/auth.ts"],
  "task_count": 4,
  "created": "2026-03-02",
  "gap_closure": false
}

2. Extract Specific Fields

Read individual fields without parsing the entire frontmatter:

get_field(.planning/phase-72/PLAN-1.md, "wave") -> 1
get_field(.planning/phase-72/PLAN-1.md, "status") -> "planned"
get_field(.planning/phase-72/PLAN-1.md, "files_modified") -> ["src/auth/oauth.ts", ...]

3. Update Fields

Update individual frontmatter fields without modifying body content:

update_field(.planning/phase-72/PLAN-1.md, "status", "executed")
update_field(.planning/phase-72/PLAN-1.md, "wave", 2)
update_field(.planning/phase-72/PLAN-1.md, "updated", "2026-03-02")

Uses Edit tool to surgically replace only the target field line.

4. Add New Fields

Add fields to existing frontmatter:

add_field(.planning/phase-72/PLAN-1.md, "executed_at", "2026-03-02T14:30:00Z")
add_field(.planning/phase-72/PLAN-1.md, "executor_agent", "gsd-executor")

Inserts new field before the closing --- delimiter.

5. Remove Fields

Remove fields from frontmatter:

remove_field(.planning/phase-72/PLAN-1.md, "gap_closure")

6. Query Across Files

Find documents matching frontmatter criteria:

query(directory: ".planning/phase-72/", field: "wave", value: 1)
-> [".planning/phase-72/PLAN-1.md", ".planning/phase-72/PLAN-2.md"]

query(directory: ".planning/", field: "status", value: "planned", recursive: true)
-> [".planning/phase-72/PLAN-1.md", ".planning/phase-73/PLAN-1.md"]

Uses Grep to search for field patterns, then validates matches.

7. Validate Frontmatter

Validate frontmatter against document type schema:

# PLAN.md required fields
required:
  - status       # planned|executing|executed|verified
  - phase        # integer or decimal
  - plan_number  # integer
  - wave         # integer (execution order group)
  - task_count   # integer

# PLAN.md optional fields
optional:
  - depends_on      # array of plan references
  - files_modified  # array of file paths
  - gap_closure     # boolean
  - created         # date
  - updated         # date
  - executed_at     # datetime

Document type schemas:

  • PLAN.md: status, phase, plan_number, wave, task_count
  • SUMMARY.md: phase, status, tasks_completed, commits
  • RESEARCH.md: phase, status, approach_count, recommended
  • STATE.md: last_updated, session_count, current_milestone
  • CONTEXT.md: phase, decisions_count, preferences

8. Batch Operations

Update frontmatter across multiple files:

batch_update(
  files: [".planning/phase-72/PLAN-1.md", ".planning/phase-72/PLAN-2.md"],
  field: "status",
  value: "executed"
)

Tool Use Instructions

Parsing Frontmatter

  1. Use Read to load the target file
  2. Extract content between first --- and second ---
  3. Parse YAML content into key-value pairs
  4. Return structured object

Updating a Field

  1. Use Read to load the file
  2. Locate the target field line within frontmatter
  3. Use Edit with the exact field line as old_string
  4. Replace with new field value line
  5. If field is multi-line (arrays), handle properly

Querying Across Files

  1. Use Glob to find candidate files in the target directory
  2. Use Grep to search for the field pattern (e.g., ^wave: 1$)
  3. For each match, verify it's within frontmatter (not body content)
  4. Return list of matching file paths

Validating Frontmatter

  1. Use Read to load the file
  2. Parse frontmatter
  3. Check required fields exist for the document type
  4. Validate field types (string, integer, array, boolean, date)
  5. Return validation result with any errors

Process Integration

  • plan-phase.js - Read/write plan frontmatter (wave, depends_on, files_modified)
  • execute-phase.js - Update plan status as execution progresses, read wave assignments for parallel execution
  • audit-milestone.js - Query all plans by status for completion checks
  • research-phase.js - Write research frontmatter (approach_count, recommended)
  • discuss-phase.js - Read phase metadata from roadmap sections

Output Format

{
  "operation": "parse|get|update|add|remove|query|validate|batch",
  "status": "success|error",
  "file": ".planning/phase-72/PLAN-1.md",
  "field": "status",
  "previousValue": "planned",
  "newValue": "executed",
  "frontmatter": {},
  "queryResults": [],
  "validation": {
    "valid": true,
    "errors": [],
    "warnings": []
  }
}

Configuration

| Setting | Default | Description | |---------|---------|-------------| | frontmatterDelimiter | --- | YAML frontmatter delimiter | | strictValidation | false | Fail on unknown fields | | autoUpdateTimestamp | true | Auto-update updated field on writes |

Error Handling

| Error | Cause | Resolution | |-------|-------|------------| | No frontmatter found | File missing --- delimiters | Add frontmatter block or skip | | YAML parse error | Malformed YAML in frontmatter | Fix YAML syntax (check indentation, colons, quotes) | | Field not found | Requested field not in frontmatter | Return null, optionally add field | | Type mismatch | Field value does not match expected type | Coerce if possible, error if not | | Edit collision | Field line not unique in file | Include surrounding context for uniqueness |

Constraints

  • Frontmatter must be valid YAML between --- delimiters at the top of the file
  • Field updates must not modify body content below the frontmatter
  • Array fields must use YAML list syntax (either inline [a, b] or block - a\n- b)
  • Date fields must use ISO 8601 format
  • Boolean fields must use true/false (not yes/no)
  • Query operations are read-only; they never modify files
  • Batch operations are atomic per file (each file update succeeds or fails independently)

Related Skills

View on GitHub
GitHub Stars1.8k
CategoryAutomation
Updated2mo ago
Forks110

Languages

JavaScript

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions