Skip to content

fix: add capabilities stanza to construct.yaml #7

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
zkSoju wants to merge 1 commit into
base: main
Choose a base branch
from
Open

fix: add capabilities stanza to construct.yaml #7

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions construct.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -56,6 +56,17 @@ events:
consumes:
- event: forge.observer.canvas_created
description: "Observer canvases inform taste token decisions"
capabilities:
model_tier: sonnet
danger_level: moderate
effort_hint: medium
downgrade_allowed: false
execution_hint: sequential
requires:
native_runtime: true
tool_calling: true
thinking_traces: false
Copy link

@chatgpt-codex-connector chatgpt-codex-connector bot Mar 21, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Advertise required thinking traces at construct level

If the 037/Echelon pipeline now gates construct admission on construct.yaml capabilities, this top-level thinking_traces: false will misclassify Artisan as runnable on trace-less runtimes even though /envisioning-direction explicitly requires traces in skills/envisioning-direction/index.yaml:55-59. In that environment the construct will be accepted, but invoking that skill will fail or be silently degraded because the pack metadata under-reports one of its contained skills' hard requirements.

Useful? React with 👍 / 👎.

vision: false
Copy link

@chatgpt-codex-connector chatgpt-codex-connector bot Mar 21, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Mark the construct as vision-capable

Several shipped skills declare vision: true (skills/iterating-visuals/index.yaml:56-60, skills/decomposing-feel/index.yaml:54-58, skills/styling-material/index.yaml:50-54, and skills/surveying-patterns/index.yaml:50-54), so publishing the pack-level manifest with vision: false under-advertises a hard runtime dependency. Any scheduler that trusts only construct.yaml can now place Artisan on a non-vision model, after which those screenshot- and image-based workflows are guaranteed to be unavailable even though the construct was accepted.

Useful? React with 👍 / 👎.

type: skill-pack
composition_paths:
reads:
Expand Down
Loading