Adoption

Agent Skills are supported by leading AI development tools.

VS Code Gemini CLI GitHub Goose Amp Cursor Claude Code Letta OpenCode Claude OpenAI Codex Factory VS Code Gemini CLI GitHub Goose Amp Cursor Claude Code Letta OpenCode Claude OpenAI Codex Factory

em-jones/structured-data

Name: structured-data
Author: em-jones

.agents/skills/structured-data/SKILL.md

npx skillsauth add em-jones/staccato-toolkit structured-data

Clean

TrivyContainer and dependency vulnerability scanner

Clean

SemgrepStatic code analysis for vulnerabilities

Clean

mcp-scan (Snyk)Model Context Protocol security validation

Skipped

Snyk (dep)Open source security scanning

Skipped

Socket.devSupply chain security analysis

Skipped

VirusTotalMulti-engine malware detection

Skipped

CrowdStrikeAdvanced threat intelligence

Skipped

OSV-ScannerOpen Source Vulnerability database check

Skipped

OWASP Dep-Check

Structured Data Patterns

Use these tools for all structured data operations. Avoid manual parsing with grep/awk/sed.

`jq` — JSON

Parse JSON output from CLI tools:

# Extract a single field
openspec status --change "my-change" --json | jq -r '.schemaName'

# Extract array elements
openspec list --json | jq -r '.[].name'

# Conditional check (exit 1 if empty)
td ls --ancestor <id> --status open --json | jq -e 'length > 0'

# Filter and transform
td ls --board "<board>" --json | jq -r '.[] | select(.status == "open") | .id + " " + .title'

`yq` — YAML

Read YAML frontmatter and entity files:

# Read a frontmatter field from a markdown file
yq -r '.td-board' openspec/changes/my-change/proposal.md

# Read a field from a catalog entity
yq -r '.metadata.name' .entities/component-platform.yaml

# List all entity names
for f in .entities/*.yaml; do
  yq -r '"\(.kind): \(.metadata.name)"' "$f"
done

# Check if a field exists
yq -r '.component // empty' openspec/changes/my-change/design.md

`md-tree` — Markdown

Extract sections from markdown files by heading. Use this instead of grep for markdown content.

The read-from-md-link skill demonstrates the canonical pattern:

# Extract a section by heading name
md-tree extract README.md "Vision"

# Extract from a change artifact
md-tree extract openspec/changes/my-change/design.md "Technology Adoption & Usage Rules"

# Extract from a spec
md-tree extract openspec/changes/my-change/specs/api/spec.md "Requirements"

Link format shorthand: README.md#Vision → md-tree extract README.md "Vision"

When to Use Each Tool

| Data source | Tool | |---|---| | openspec CLI output | jq | | td CLI output (--json) | jq | | YAML entity files (.entities/) | yq | | Markdown frontmatter | yq | | Markdown section content | md-tree extract | | devbox.json, package.json | jq | | go.mod | grep (no structured tool; direct text) |

Guardrails

Always use --json / -o yaml flags when available on CLI tools
Prefer jq -r (raw output, no quotes) for string values; omit -r when piping JSON to next command
Use yq -r for scalar values; omit -r when the output will be further processed as YAML
md-tree extract returns the full subtree under the heading — pipe to md-tree again to narrow further if needed
Do not use cat + manual parsing when a structured tool is available

em-jones/structured-data

.agents/skills/structured-data/SKILL.md

Patterns for extracting and processing structured data from CLI tools. Use jq for JSON, yq for YAML, and md-tree for Markdown. Apply these patterns instead of manual parsing to reduce token usage and improve clarity.

1 stars

tools

Updated Apr 17, 2026

$ install --global

skillsauth

npx skillsauth add em-jones/staccato-toolkit structured-data

Install this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.

Security Scan Results

3 of 9 scanners reported clean

Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.

Scanners Passed

Scanners in report

Clean

TrivyContainer and dependency vulnerability scanner

95%

Clean

SemgrepStatic code analysis for vulnerabilities

95%

Clean

mcp-scan (Snyk)Model Context Protocol security validation

95%

Skipped

Snyk (dep)Open source security scanning

50%

Skipped

Socket.devSupply chain security analysis

50%

Skipped

VirusTotalMulti-engine malware detection

50%

Skipped

CrowdStrikeAdvanced threat intelligence

50%

Skipped

OSV-ScannerOpen Source Vulnerability database check

50%

Skipped

OWASP Dep-Check

50%

Last scanned: Apr 17, 2026, 5:15 AM7.5s1 file scanned

SKILL.md

name:: structured-data
description:: Patterns for extracting and processing structured data from CLI tools. Use jq for JSON, yq for YAML, and md-tree for Markdown. Apply these patterns instead of manual parsing to reduce token usage and improve clarity.
compatibility:: opencode
maturity:: stable

Structured Data Patterns

Use these tools for all structured data operations. Avoid manual parsing with grep/awk/sed.

`jq` — JSON

Parse JSON output from CLI tools:

# Extract a single field
openspec status --change "my-change" --json | jq -r '.schemaName'

# Extract array elements
openspec list --json | jq -r '.[].name'

# Conditional check (exit 1 if empty)
td ls --ancestor <id> --status open --json | jq -e 'length > 0'

# Filter and transform
td ls --board "<board>" --json | jq -r '.[] | select(.status == "open") | .id + " " + .title'

`yq` — YAML

Read YAML frontmatter and entity files:

# Read a frontmatter field from a markdown file
yq -r '.td-board' openspec/changes/my-change/proposal.md

# Read a field from a catalog entity
yq -r '.metadata.name' .entities/component-platform.yaml

# List all entity names
for f in .entities/*.yaml; do
  yq -r '"\(.kind): \(.metadata.name)"' "$f"
done

# Check if a field exists
yq -r '.component // empty' openspec/changes/my-change/design.md

`md-tree` — Markdown

Extract sections from markdown files by heading. Use this instead of grep for markdown content.

The read-from-md-link skill demonstrates the canonical pattern:

# Extract a section by heading name
md-tree extract README.md "Vision"

# Extract from a change artifact
md-tree extract openspec/changes/my-change/design.md "Technology Adoption & Usage Rules"

# Extract from a spec
md-tree extract openspec/changes/my-change/specs/api/spec.md "Requirements"

Link format shorthand: README.md#Vision → md-tree extract README.md "Vision"

When to Use Each Tool

Guardrails

Always use --json / -o yaml flags when available on CLI tools
Prefer jq -r (raw output, no quotes) for string values; omit -r when piping JSON to next command
Use yq -r for scalar values; omit -r when the output will be further processed as YAML
md-tree extract returns the full subtree under the heading — pipe to md-tree again to narrow further if needed
Do not use cat + manual parsing when a structured tool is available

Related Skills

em-jones/.agents/skills/vite-plus

tools

VerifiedTrustedCommunity

# Using Vite+, the Unified Toolchain for the Web This project is using Vite+, a unified toolchain built on top of Vite, Rolldown, Vitest, tsdown, Oxlint, Oxfmt, and Vite Task. Vite+ wraps runtime management, package management, and frontend tooling in a single global CLI called `vp`. Vite+ is distinct from Vite, but it invokes Vite through `vp dev` and `vp build`. ## Vite+ Workflow `vp` is a global binary that handles the full development lifecycle. Run `vp help` to pr

1SKILL.mdUpdated Apr 17, 2026

em-jones/.agents/skills/vite-plus

em-jones/ui-data-tables

development

VerifiedTrustedCommunity

Guide for building performant data tables. Uses tanstack-table for table logic (sorting, filtering, pagination) and tanstack-virtual for rendering large datasets efficiently.

1SKILL.mdUpdated Apr 17, 2026

em-jones/ui-data-tables

em-jones/typescript-effect-library

development

VerifiedTrustedCommunity

Expert guidance for building observable, expressive, and fault-tolerant TypeScript applications using the effect-ts/effect ecosystem. Covers Effect<A, E, R> type, error management, dependency injection via Layers, observability (logging, metrics, tracing), concurrency with Fibers, retry/scheduling, Schema validation, Streams, and Sinks.

1SKILL.mdUpdated Apr 17, 2026

em-jones/typescript-effect-library

em-jones/typescript-e2e-testing

tools

VerifiedTrustedCommunity

Complete E2E (end-to-end) and integration testing skill for TypeScript/NestJS projects using Jest, real infrastructure via Docker, and GWT pattern. ALWAYS use this skill when user needs to: **SETUP** - Initialize or configure E2E testing infrastructure: - Set up E2E testing for a new project - Configure docker-compose for testing (Kafka, PostgreSQL, MongoDB, Redis) - Create jest-e2e.config.ts or E2E Jest configuration - Set up test helpers for database, Kafka, or Redis - Configure .env.e2e environment variables - Create test/e2e directory structure **WRITE** - Create or add E2E/integration tests: - Write, create, add, or generate e2e tests or integration tests - Test API endpoints, workflows, or complete features end-to-end - Test with real databases, message brokers, or external services - Test Kafka consumers/producers, event-driven workflows - Working on any file ending in .e2e-spec.ts or in test/e2e/ directory - Use GWT (Given-When-Then) pattern for tests **REVIEW** - Audit or evaluate E2E tests: - Review existing E2E tests for quality - Check test isolation and cleanup patterns - Audit GWT pattern compliance - Evaluate assertion quality and specificity - Check for anti-patterns (multiple WHEN actions, conditional assertions) **RUN** - Execute or analyze E2E test results: - Run E2E tests - Start/stop Docker infrastructure for testing - Analyze E2E test results - Verify Docker services are healthy - Interpret test output and failures **DEBUG** - Fix failing or flaky E2E tests: - Fix failing E2E tests - Debug flaky tests or test isolation issues - Troubleshoot connection errors (database, Kafka, Redis) - Fix timeout issues or async operation failures - Diagnose race conditions or state leakage - Debug Kafka message consumption issues **OPTIMIZE** - Improve E2E test performance: - Speed up slow E2E tests - Optimize Docker infrastructure startup - Replace fixed waits with smart polling - Reduce beforeEach cleanup time - Improve test parallelization where safe Keywords: e2e, end-to-end, integration test, e2e-spec.ts, test/e2e, Jest, supertest, NestJS, Kafka, Redpanda, PostgreSQL, MongoDB, Redis, docker-compose, GWT pattern, Given-When-Then, real infrastructure, test isolation, flaky test, MSW, nock, waitForMessages, fix e2e, debug e2e, run e2e, review e2e, optimize e2e, setup e2e

1SKILL.mdUpdated Apr 17, 2026

em-jones/typescript-e2e-testing

Download

For Claude Desktop. Download once, then upload the file in the app — no terminal needed.

Need help? View full Cowork setup guide →

Install manually

Choose your platform

# Clone the repo
git clone https://github.com/em-jones/staccato-toolkit.git

# Copy into Claude Code skills folder (global)
cp -r staccato-toolkit/.agents/skills/structured-data ~/.claude/skills/

Claude Code Skills — official skills path docs.

Repository

em-jones/staccato-toolkit

1 stars

Compatible with

Claude Code

OpenAI Codex CLI

ChatGPT

Adoption

em-jones/structured-data

$ install --global

Security Scan Results

SKILL.md

Structured Data Patterns

jq — JSON

yq — YAML

md-tree — Markdown

When to Use Each Tool

Guardrails

Related Skills

em-jones/.agents/skills/vite-plus

em-jones/ui-data-tables

em-jones/typescript-effect-library

em-jones/typescript-e2e-testing

em-jones/structured-data

$ install --global

Security Scan Results

SKILL.md

Structured Data Patterns

jq — JSON

yq — YAML

md-tree — Markdown

When to Use Each Tool

Guardrails

Related Skills

em-jones/.agents/skills/vite-plus

em-jones/ui-data-tables

em-jones/typescript-effect-library

em-jones/typescript-e2e-testing

`jq` — JSON

`yq` — YAML

`md-tree` — Markdown

`jq` — JSON

`yq` — YAML

`md-tree` — Markdown