feat(native): introduce system native skills - #22
Merged
Conversation
datbth
force-pushed
the
native-skills/write-dashboard
branch
from
July 16, 2026 10:25
66c33fc to
87685e1
Compare
datbth
marked this pull request as ready for review
July 29, 2026 12:01
|
Caution The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased. |
… skill
Replaces the write-dashboard body with the merged build_dashboard skill
developed and evaluated in the staging3 workspace. Same slot, same
frontmatter name, so it takes over rather than competing.
Evidence, from a 64-run eval against the staging3 Copilot:
- the two skills were competing and write-dashboard won 53 of 64 runs.
The staging3 skill fired 0 times on precise intermediate/complex
prompts because its description carried an anti-trigger disclaiming
exactly those asks; when it did win it scored 14/18 correct vs 15/46
otherwise
- the anti-trigger is now cut on a different axis - "is a dashboard the
deliverable?" - rather than excluding facets of the dashboard job
- all 12 underspecified runs opened with a KPI row and closed with a
table, only the middle varying. The input checklist named the four
questions rather than asking for them, and the minimum output
prescribed the KPI-row frame outright. Both are gone: the reader's
job (monitoring, diagnosing, comparing, planning, looking up) is now
decided first, questions are derived and ranked, and the minimum is
stated as a quality bar rather than a shape
What the previous version contributed and this keeps: the block-type
vocabulary, the four ref: forms, the layout constructs, and the worked
example - now conforming to the skill's own prescriptions (1220 grid,
TabLayout, classic theme, no FilterBlock default, complete interactions).
Dropped from the previous version: "prefer the smallest set of blocks"
(conflicts with the completeness bar), interactions as optional, and the
standalone 107-line example that contradicted the layout conventions.
Not carried over: the @context: viz-reuse mechanism. The token was wrong
(the resource type is VizAml) and, more importantly, every @context:
occurrence in the product is an MCP tool parameter - a runtime hand-off
between tool calls, not something that resolves inside a saved page.aml.
It is also gated behind FT_REUSE_CONTEXT. The version on the
native-skills/write-dashboard branch still documents it.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
The skill's content is now the merged build_dashboard skill, so the identity should match. Repo convention is kebab-case folders with a matching frontmatter `name`, and the runtime normalises that to an underscored skill_id — so `build-dashboard` here surfaces to the agent as `build_dashboard`, the same way `write-dashboard` surfaced as `write_dashboard`. This removes the write-dashboard slot rather than shadowing it, so only one dashboard-building skill remains and the two no longer compete. Nothing else in the repo referenced the old name. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
- description trimmed (~20% shorter), same four-part structure. Kept "chart, KPI, table" and "filter or date control" in the trigger surface deliberately — those phrasings are what the eval showed the previous description was losing on. - dropped the "complete layout vocabulary" claim. The list is now explicitly not exhaustive, so the skill no longer needs updating on every layout feature release; the don't-invent guardrail and the search_docs check stay, since inventing `margin`/`padding`/`gap` was a real failure. - softened the per-chart filter rule to a preference, per review. It now scopes to the actual failure — a hard-coded time window or comparison period ships empty or goes stale — and explicitly allows a filter that defines what the chart is (top 10, one segment). Also updated two places that restated the same rules: the verify step and the worked-example heading. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.