Przejdź do treści
Biblioteka skilli
AI i agenci · Budowanie i kod

vertical-creator

/vertical-creator

Tworzy i przegląda definicje pionów Harness Anything: JSON, źródła ukończenia, katalogi szablonów i schematy projekcji.

Licencja
AGPL-3.0
Ostatnia zmiana repozytorium
27.10.2026

Ocena i bezpieczeństwo

100/ 100Klasa: dobry
Format25 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść35 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
Pliki w paczce
2
Skrypty
0
Komentarze HTML
0
Adresy URL w SKILL.md
0
Przestarzałość

Brak sygnałów. Repozytorium zmienione 27.10.2026, bez odwołań do wycofanych modeli i API.

Licencja

AGPL-3.0, copyleft: przeróbki udostępniane innym muszą mieć tę samą licencję.

Co robi i kiedy

Tworzy i przegląda definicje pionów Harness Anything: JSON, źródła ukończenia, katalogi szablonów i schematy projekcji.

Oryginalny opis (EN)

Create, review, or update Harness Anything verticals. Use when designing vertical-definition JSON, declarative completion sources and gates, template catalogs, entity kinds, package scaffolds, projection schemas, and preset layering for a new Harness Anything domain such as coding, QA, docs, design, or operations.

Jak działa

  1. Core Rule
  2. Workflow
  3. Entity Declaration Tuple
  4. Vertical Definition Pattern
  5. Template Catalog v2
  6. Design Rules
  7. Review Checklist
Sekcje z nagłówków SKILL.md, w oryginale · 256 linii, 1 154 słów
Podgląd SKILL.md
---
name: vertical-creator
description: Create, review, or update Harness Anything verticals. Use when designing vertical-definition JSON, declarative completion sources and gates, template catalogs, entity kinds, package scaffolds, projection schemas, and preset layering for a new Harness Anything domain such as coding, QA, docs, design, or operations.
---

# Vertical Creator

## Core Rule

Keep verticals declarative. A vertical defines entity shape, template catalogs, scaffolds, defaults, and applicable presets. It must not require CLI core branches for a specific domain.

The CLI may provide only generic vertical infrastructure:

- Schema validation.
- Template catalog loading.
- Template materialization.
- Settings/dev-mode gating.
- Generic preset and profile selection.

Vertical-specific behavior belongs in vertical assets, template catalogs, preset manifests, and declared process scripts. A vertical's `completion.sources`, `completion.gates`, and `completion.closeoutDefaults` describe domain checks; a preset profile selects gate ids. Keep the source and gate declarations in the package that owns their domain meaning, and keep execution inside a declared preset entrypoint.

A vertical asset root must include `vertical.json`, `template-catalog.json`, and
`capabilities.json`. The catalogs are required even when a vertical has no
templates or command providers; use empty arrays for those catalogs. When a
completion command emits `completion-witness`, declare its provider in
`capabilities.json` with the action kind and exact payload fields, as shown
below.

## Workflow

1. Name the domain and list its entity kinds using the entity declaration tuple.
2. Decide which entities are lifecycle package entities and which are schema-only metadata entities.
3. Define package scaffolds and repository roots for every lifecycle entity.
4. Put template bodies in Markdown assets under `assets/<vertical>/templates/<slot>/<locale>.md`.
5. Register those assets in `template-catalog/v2` with `bodyPath`; do not use inline `body`.
6. Define required documents as `templateSelections` that point at catalog refs.
7. Define domain completion sources, gates, and closeout defaults in `completion`; profiles select gates by id.
8. Define applicable presets separately as `preset-manifest/v3`; put profile-specific gate selection in `profiles[].completionGates`.
9. Run `ha vertical validate --source <vertical-directory> --preset <installed-preset-id>` to check the vertical and its completion source catalog.
10. Add validation tests for schema shape, source/entrypoint references, materialized paths, catalog body paths, and default preset/profile behavior.
11. Add integration tests only for real CLI/filesystem behavior. See [gate-customization](../gate-customization/SKILL.md) for a complete artifact-only research gate.

## Entity Declaration Tuple

Declare each entity with the v2 five-part contract:

- `id`
- `entityType`
- `packageKind` for lifecycle entities or `schemaRef` for schema entities
- `contractEntity`
- matching scaffold/root membership where required

Lifecycle entities must have both a `packageScaffolds` entry and a `repositoryScaffold.entityRoots` entry. Schema entities must not have package scaffolds or repository roots.

## Vertical Definition Pattern

A vertical package contains `vertical.json` and its catalog/assets. Validate the package directory with `ha vertical validate --source <package-directory>`; this fragment illustrates the declaration shape.

```json
{
  "schema": "vertical-definition/v1",
  "id": "example/work",
  "title": "Example Work",
  "version": "1.0.0",
  "entityFieldExtensions": [],
  "entityKinds": [
    {
      "id": "task",
      "entityType": "lifecycle",
      "packageKind": "task-package/v2",
      "contractEntity": true
    },
    {
      "id": "fact",
      "entityType": "schema",
      "schemaRef": "schema://fact-record",
      "contractEntity": true
    }
  ],
  "contractEntityKinds": ["task", "fact"],
  "packageScaffolds": [
    {
      "entityKind": "task",
      "templateSelections": []
    }
  ],
  "repositoryScaffold": {
    "entityRoots": [
      {
        "entityKind": "task",
        "path": "{{paths.tasksRoot}}",
        "create": "init"
      }
    ],
    "dirs": [],
    "seededDocs": []
  },
  "scripts": [],
  "templateSelections": [],
  "completion": {
    "sources": {},
    "gates": {},
    "closeoutDefaults": {}
  },
  "projectionSchemas": []
}
```

The same package root also needs both runtime catalogs. For an artifact-only
command gate, the provider declaration is:

```json
{
  "schema": "preset-capabilities/v1",
  "providers": [
    {
      "id": "completion-witness",
      "kind": "checker",
      "version": "1",
      "actionKind": "completion-witness",
      "payloadFields": ["result", "subjects", "predicateType", "predicate", "diagnostic"]
    }
  ]
}
```

`template-catalog.json` uses `template-catalog/v2`, a package record, and a
`documents` array. A vertical with no templates may use `"documents": []`;
otherwise register each Markdown body under its `bodyPath` as shown in the
Template Catalog v2 example. Do not omit either catalog file: runtime loading
requires both before it can validate the vertical and its completion sources.

Validate it:

```sh
ha vertical validate --source <package-directory>
```

## Template Catalog v2

A vertical package should keep bodies as Markdown assets and register them by `bodyPath`:

```text
assets/software-coding/
  vertical.json
  template-catalog.json
  templates/
    task.plan/
      en-US.md
      zh-CN.md
  presets/
    standard-task/
      preset.json
```

Catalog root:

```json
{
  "schema": "template-catalog/v2",
  "package": {
    "id": "software-coding-core",
    "title": "Software Coding Core Templates",
    "version": "1.0.0",
    "owner": "harness-anything",
    "locales": ["zh-CN", "en-US"]
  },
  "documents": [
    {
      "id": "planning/task-plan",
      "version": "1",
      "documentKind": "task-plan",
      "slot": "task.plan",
      "materializeAs": "task_plan.md",
      "frontmatterSchema": "task-package/v2",
      "requiredAnchors": ["## Goal", "## Verification"],
      "fallbackLocale": "en-US",
      "locales": [
        {
          "locale": "en-US",
          "anchors": ["## Goal", "## Verification"],
          "bodyPath": "templates/task.plan/en-US.md"
        },
        {
          "locale": "zh-CN",
          "anchors": ["## Goal", "## Verification"],
          "bodyPath": "templates/task.plan/zh-CN.md"
        }
      ]
    }
  ]
}
```

`templates/task.plan/en-US.md` must contain all required anchors:

```md
## Goal

Describe the target outcome.

## Verification

List the validation steps.
```

Preset overlays should reference the same catalog documents from `preset-manifest/v3` profiles:

```json
{
  "id": "baseline",
  "title": "Baseline",
  "completionGates": [],
  "templateSelections": [
    {
      "slot": "task.plan",
      "templateRef": "template://planning/task-plan@1",
      "materializeAs": "task_plan.md",
      "localePolicy": { "prefer": "project", "fallback": "en-US" }
    }
  ]
}
```

## Design Rules

- Use templates for document structure, not ad hoc file writes.
- Use presets for optional process or content overlays.
- Use `preset-manifest/v3` for all new preset examples.
- Use `template-catalog/v2` with `bodyPath`; never teach inline template `body`.
- Keep domain source and gate IDs in the declarative `completion` object; do not add a vertical-id branch to the CLI.
- For command-backed completion, point a source at an installed preset entrypoint that produces `completion-witness`; the declaration alone does not grant runtime permissions.
- Use `resultSchema.required` for required predicate fields and `gates.<id>.bindings` when a predicate value must equal a JSON Pointer value in a frozen submitted artifact.
- `completion.closeoutDefaults` may set `review`, `consent`, and `factDisposition`; repository and task-profile choices take precedence over domain defaults.
- Keep template `requiredAnchors` in the template catalog. They validate document structure and are separate from completion predicate schema requirements.
- Keep project/user overrides additive and fail closed on invalid active overrides.
- Do not promise unattended conversion when the system supports Legacy Intake plus explicit rebuild only.
- Keep private harness operating state out of public docs unless explicitly designing public product documentation.

## Review Checklist

- `ha vertical validate --source <package-directory>` passes.
- Entity kinds declare `entityType` and exactly one of `packageKind` or `schemaRef`.
- Every lifecycle entity has a package scaffold and repository root.
- Schema entities do not declare package scaffolds or repository roots.
- Template refs exist in `template-catalog/v2` and use asset-backed `bodyPath`.
- Required anchors match locale anchors and appear in each body asset.
- Presets shipped with the vertical use `preset-manifest/v3`, `profiles`, and
  `defaultProfile`; every v3 profile explicitly declares `completionGates`, even
  when empty (ADR-0027 D7).
- Preset manifests pass `ha preset validate --source <package-directory>`.
- The vertical works without CLI branches keyed by vertical id.
- Template refs exist in the catalog and materialize to stable paths.
- Default preset/profile behavior is explicit.
- Every `completion.gates.<id>.source` resolves to one declared source, and every command source resolves to an installed preset entrypoint.
- Predicate JSON Schemas and artifact bindings express only domain checks; authorization and runner authority remain outside the vertical package.
- The completion example's profile selects the declared gate id; it does not duplicate source or gate declarations.
- Custom verticals remain gated by user dev mode and project settings.
- Tests are placed in the proper tier manifest when new test files are added.
Pliki w paczce (2)
  • SKILL.md 10 KB
  • agents/openai.yaml 1 KB

Wersje

W bazie nie ma innych skilli o nazwie vertical-creator.

Migawka bazy z 13.11.2026 · wersja paczki c3fc712e16b3 (skrót SHA-256 całej paczki)

Pobrania w ostatnich 30 dniach: 0 · ranking

Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.

Podobne skille

  • 100preset-creator
    Tworzy, sprawdza i aktualizuje pakiety presetów Harness Anything w wersji preset-manifest/v3: profile, bramki ukończenia, szablony, skrypty i testy.
  • 100preset-trigger
    Rozpoczyna tworzenie zadania Harness Anything od wyboru presetu programistycznego, przy tworzeniu lub planowaniu pakietu zadania.
  • 100add-harness-package
    Prowadzi przez dodanie nowego pakietu harness @ai-sdk/harness-<name> w AI SDK, który dopasowuje środowisko uruchomieniowe agenta kodującego do interfejsu HarnessV1.
  • 100skill-to-plugin
    Generuje plugin dla narzędzia do kodowania z istniejącego skilla na podstawie lokalnych szablonów.
  • 90coding-agent-harness
    Projektuje harness agenta kodującego: ograniczenia, weryfikację i bazę akceptacji oraz ocenia, które zadania nadają się dla agenta.
  • 100agent-harness-design
    Pomaga projektować definicje narzędzi dla nowego agenta lub subagenta i recenzować harness przy wysokim odsetku ponowień, niejednoznacznych wywołaniach i cichych awariach.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.