Results for “yaml-validation”

Publishes agent skills to GitHub with automatic validation of SKILL.md, README quality checks, repository creation or updates, and real installation verification via npx skills.

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

YAML configuration for CI/CD, Docker Compose, and Kubernetes.

Schema validation for notes. Checks against domain-specific templates. Validates required fields, enum values, description quality, and link health. Non-blocking — warns but doesn't prevent capture. Triggers on "/validate", "/validate [note]", "check schema", "validate note", "validate all".

Validate data with Yup schemas. Use when adding form validation, defining API request schemas, validating configuration, or building type-safe validation pipelines in JavaScript/TypeScript.

Write, read, and validate HUML documents, converting between YAML/JSON/TOML and HUML for human-readable configuration files.

Validate, review, and compare DESIGN.md design-system files using the Google `@google/design.md` specification and CLI. Trigger this skill whenever the user asks to lint / validate / verify / check / review / diff a `DESIGN.md` (case-insensitive), mentions "design.md", "design system spec", "design tokens YAML", "WCAG contrast on tokens", or uses Korean phrases like "DESIGN.md 검증", "디자인 시스템 검사", "디자인 토큰 점검", "design.md 린트". Also fire when the user pastes a YAML front-matter block that looks like a design-token document (top-level `colors:` / `typography:` / `components:` keys) or when a DESIGN.md file appears in the workspace and the conversation turns to validating, comparing, or shipping it. Covers YAML front matter, markdown section order, token references, component property validity, WCAG contrast findings, missing primary colors or typography, orphaned tokens, and regressions between two DESIGN.md versions.

Scaffolds eval.yaml test files for agent skills in the dotnet/skills repository, including scenario writing, assertion definition, and rubric creation.

Executes Atomic Red Team tests for MITRE ATT&CK technique validation using the atomic-operator Python framework. Loads test definitions from YAML atomics, runs attack simulations, and validates detection coverage.

Turns a natural-language request into one or more coder-eval task YAML files with minimal prompts and weighted success criteria, validated against the coder-eval CLI.

Author/validate/export Google's DESIGN.md token spec files.

Verify tasks marked [X] in tasks.md are implemented, not phantom completions (marked done but backed by missing or dead code).

Deploys and manages Falco YAML rules for runtime threat detection in containers and Kubernetes, monitoring syscalls for shell spawns, file tampering, network anomalies, and privilege escalation. Parses Falco alerts for incident response.

Author/validate/export Google's DESIGN.md token spec files.

Runs bottom-up type-chain validation across database, hooks, and UI layers, then fixes errors at the failing layer for project health checks before large changes.

Centralized JSON validation for AGENT_SUCCESS_CRITERIA with defensive parsing and injection attack prevention (CVSS 8.2)

Iterates through pending development plans in .cursor/plans, implementing tasks, running self-tests, reviewing code, committing locally, and moving completed plans to docs/plans/done.

Implement secure JWT signing and verification with HMAC-SHA256, RSA-PSS, and EdDSA, including token expiration, claims validation, and defense against common JWT attacks.

You are an expert in Soda, the data quality platform for testing, monitoring, and profiling data. You help developers write data quality checks in YAML that validate freshness, completeness, uniqueness, validity, and business rules — catching data issues before they reach dashboards and ML models.

Use only for video game projects; plan Steam/store page, capsule, trailer, screenshot, tag, and wishlist validation

Yup schema validation library. Popular with Formik for form validation. Use when building forms with React/Formik or needing schema-based validation. USE WHEN: user mentions "Yup", "Formik validation", asks about "yup schema", "Formik setup", "form validation library" DO NOT USE FOR: Zod projects (use zod skill), NestJS/class-validator (use class-validator skill), new projects (prefer Zod)

Validate whether an OSS tool is worth building through staged namespace, existing-solution, and feasibility review

Documents the required and optional keys for defining unit tests in a dbt YAML schema file.

Author/validate/export Google's DESIGN.md token spec files.

Guides testing Megatron-LM: test layout, recipe YAML, adding and running unit/functional tests, golden values, marker filters, and CI parity.

Create and modify NeMo AutoModel training and evaluation recipes, including YAML structure, builders, and execution flow.

Verify tasks marked [X] in tasks.md are implemented, not phantom completions (marked done but backed by missing or dead code).

Use only for video game projects; map genre conventions, player expectations, review complaints, and anti-patterns

Use Geniml for audited local genomic-interval workflows: validate BED and universe contracts, plan Region2Vec or scEmbed runs, inspect model/tokenizer compatibility, and assess consensus universes.

Use only for developer-facing products; map users, buyers, champions, contributors, and operational stakeholders

Evaluates open-ended generation quality of multilingual LLMs across brainstorming, planning, and long-form tasks, using AYA and DOLLY datasets with qualitative fluency and quality scoring.