v3-1-skos-fixture

Validate SKOS v3.1 relation predicates in generated manifests.

1|Updated May 6, 2026
One-click install
npx skills add https://github.com/jacob-balslev/skill-graph --skill v3-1-skos-fixture
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: v3-1-skos-fixture
Source: https://github.com/jacob-balslev/skill-graph/tree/main/examples/tests/v3-1-skos-fixture
Command: npx skills add https://github.com/jacob-balslev/skill-graph --skill v3-1-skos-fixture

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a stable SKOS fixture that helps ensure the manifest generator, lint checks, and router logic correctly recognize and validate the full v3.1 predicate set and the ADR-defined relation semantics.

Core Features & Use Cases

  • SKOS predicate coverage: Exercises key v3.1 predicates including related, broader, and narrower, ensuring they appear in generated manifest relation blocks.
  • ADR semantics verification: Validates the boundary/disjoint_with split, where boundary targets routing-layer ownership and disjoint_with represents OWL class disjointness.
  • Deterministic test fixture usage: Designed to be consumed by repository scripts (not a production authored skill) for runtime recognition and relation-target validation.

Quick Start

Use the v3-1-skos-fixture skill to run the companion test scripts that assert each v3.1 SKOS predicate is correctly emitted and validated in the generated manifest.

Frequently Asked Questions about v3-1-skos-fixture

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate SKOS semantic relations in a generated manifest?

Validate SKOS semantic relations in a generated manifest by running a deterministic test fixture that asserts v3.1 predicates like broader, narrower, and related are correctly emitted and recognized during lint checks and routing map generation.

What is the difference between boundary and disjoint_with in SKOS relation validation?

In SKOS relation validation, boundary targets routing-layer ownership while disjoint_with represents OWL class disjointness. Test fixtures verify this ADR-defined split to ensure correct semantic predicate handling across the library.

How do I test YAML frontmatter parsing for SKOS predicate recognition?

Test YAML frontmatter parsing for SKOS predicate recognition by executing round-trip checks between SKILL.md files and compiled manifest output. This validates relation-target resolution for predicates like depends_on and verify_with.

Can I use a test fixture to verify routing map logic for SKOS v3.1 predicates?

Yes, you can use a deterministic test fixture to verify routing map logic for SKOS v3.1 predicates. It exercises automated test scenarios that assert related, broader, and narrower predicates are correctly validated during routing checks.

What SKOS predicates are covered by automated lint validation checks?

Automated lint validation checks cover the full v3.1 SKOS predicate set, including related, broader, narrower, boundary, disjoint_with, verify_with, and depends_on. These predicates are validated against ADR-defined relation semantics.