New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Pre Scaffold Openspec Coherence Check

by BlackBeltTechnology in BlackBeltTechnology/pi-agent-dashboard

Run before scaffolding any OpenSpec proposal to catch duplicates of archived work and contradictions with shipped architecture.

MITAuto-check passedSales & Support

Install Pre Scaffold Openspec Coherence Check

skills CLI
$ npx skills add BlackBeltTechnology/pi-agent-dashboard --skill pre-scaffold-openspec-coherence-check -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install BlackBeltTechnology/pi-agent-dashboard pre-scaffold-openspec-coherence-check --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/BlackBeltTechnology/pi-agent-dashboard.git skills-src && mkdir -p .claude/skills && cp -r skills-src/packages/openspec-workflow/.pi/skills/pre-scaffold-openspec-coherence-check .claude/skills/pre-scaffold-openspec-coherence-check && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
pre-scaffold-openspec-coherence-check
GitHub stars
315
Token cost
~1.5k tokens
SKILL.md length
749 words
Files
1
Skills in repo
70
Repo updated
First seen
Licence
MIT

At a glance

Run before scaffolding any OpenSpec proposal to catch duplicates of archived work and contradictions with shipped architecture.

  • Works in 7 steps: Archive sweep: ls… → Active sweep: openspec list | grep -iE… → Current-code verification (for behaviour… → …
  • Tasks that involve Project scaffolding
  • SKILL.md covers When to Use, Procedure, Pitfalls and Verification
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Pre Scaffold Openspec Coherence Check is an agent skill from BlackBeltTechnology/pi-agent-dashboard. Run before scaffolding any OpenSpec proposal to catch duplicates of archived work and contradictions with shipped architecture. Always run when about to create openspec/changes/<name/, especially for proposals touching a subsystem with a recent archive entry. Triggers: 'scaffold OpenSpec', 'write a proposal', 'create change', 'openspec change new'.

Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Sales & Support, covering Project scaffolding and Proposals and quotes. The repository describes itself as: Real-time web dashboard for pi coding-agent sessions. Multi-session view, live chat mirroring, integrated terminal, diff viewer, pi-flows execution, and mobile-first remote… The licence is MIT.

When your agent uses it

  • Tasks that involve Project scaffolding
  • Tasks that involve Proposals and quotes

Example prompts

  • “scaffold OpenSpec”
  • “write a proposal”
  • “create change”
  • “/pre-scaffold-openspec-coherence-check”

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

  1. Archive sweep: ls openspec/changes/archive/ | grep -iE ‘&lt;topic-keywords&gt;’. For tool-renderer / plugin-slot / MCP / ctx_* /…
  2. Active sweep: openspec list | grep -iE ‘&lt;topic-keywords&gt;’. Read any active change that overlaps so the new proposal does not collide…
  3. Current-code verification (for behaviour claims): if the proposal says ‘X is not wired’, ‘Y never fires’, ‘Z falls through to Generic’…
  4. Slot-prop contract check: cat packages/shared/src/dashboard-plugin/slot-props.ts and read SlotPropsMap[‘&lt;slot&gt;’]. Confirm the…
  5. Registry check (built-in renderers): cat packages/client/src/components/tool-renderers/registry.ts. The ctx_* family is mapped to a single…
  6. Architecture-choice review: when the topic intersects an existing implementation, search recent commits with git log --oneline…
  7. Optional but recommended: run the spec-coherence-check skill (project skill) which sweeps all active proposals for staleness, conflicts…

What it can do on your machine

Read from SKILL.md and the folder at commit 7a2d171. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Pre Scaffold Openspec Coherence Check loads about 1.5k tokens when it runs. Until then it costs about 97 tokens; SKILL.md has 749 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~97
When it runs · the whole SKILL.md, loaded when a task matches
~1.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from BlackBeltTechnology/pi-agent-dashboard at commit 7a2d171, republished under its MIT licence (© BlackBeltTechnology). 749 words, ~1,536 tokens.

Download SKILL.mdSave it as .claude/skills/pre-scaffold-openspec-coherence-check/SKILL.md (or your agent's skills folder).
name
pre-scaffold-openspec-coherence-check
description
Run before scaffolding any OpenSpec proposal to catch duplicates of archived work and contradictions with shipped architecture. Always run when about to create openspec/changes/<name>/, especially for proposals touching a subsystem with a recent archive entry. Triggers: 'scaffold OpenSpec', 'write a proposal', 'create change', 'openspec change new'.
version
1
created
2026-06-13
updated
2026-06-13

When to Use

Use before scaffolding any new OpenSpec change in this project, regardless of whether the topic feels novel. Two of the most damaging mistakes the assistant has made are (a) re-proposing work that already shipped and was archived, and (b) basing claims about current code on stale file-index harvests or grep results that miss the actual wiring idiom. This skill front-loads the cheap checks that would have caught both.

Trigger this skill when about to run any of: openspec change new, Write to openspec/changes/<name>/proposal.md, the openspec-new-change skill, the openspec-ff-change skill, or any drafted "## Why / ## What Changes" markdown that will become a proposal.

Do NOT skip even when the explore-mode conversation feels grounded. The Explore subagent harvests the file-index which can be days stale; the main agent's own grep can answer the wrong question (e.g. grepping for a consumer component when the wiring is inline).

Procedure

  1. Archive sweep: ls openspec/changes/archive/ | grep -iE ‘<topic-keywords>’. For tool-renderer / plugin-slot / MCP / ctx_* / context-mode topics specifically check for 2026-06-05-wire-tool-renderer-slot and 2026-06-05-add-ctx-tool-renderer. If any archive entry matches the topic, READ its proposal.md before writing a new one.
  2. Active sweep: openspec list | grep -iE ‘<topic-keywords>’. Read any active change that overlaps so the new proposal does not collide on filename, capability, or scope.
  3. Current-code verification (for behaviour claims): if the proposal says ‘X is not wired’, ‘Y never fires’, ‘Z falls through to Generic’, grep for the FUNCTIONAL pattern not just the named component. For tool-renderer claims specifically: grep -rn 'getClaims.*tool-renderer\|forToolName' packages/client/src/components/ToolCallStep.tsx and read the current dispatch block (lines 90–120). The slot wiring inlines useSlotRegistryOrNull + forToolName + claimShouldRender; the ToolRendererSlot consumer component is unused, but that does NOT mean the slot is unwired.
  4. Slot-prop contract check: cat packages/shared/src/dashboard-plugin/slot-props.ts and read SlotPropsMap[‘<slot>’]. Confirm the required fields (every slot requires pluginContext: AnyPluginContext) and the optional fields. Do not invent a contract.
  5. Registry check (built-in renderers): cat packages/client/src/components/tool-renderers/registry.ts. The ctx_* family is mapped to a single CtxToolRenderer with a ctx_-prefix safety net for new tool names. Honour this architecture choice unless explicitly proposing to revisit it.
  6. Architecture-choice review: when the topic intersects an existing implementation, search recent commits with git log --oneline --since=<30 days> -- <relevant paths> to understand which design the team picked and the rationale. The choice between core built-in vs plugin for ctx_* was DELIBERATE (high-frequency tool, hot path); do not propose to reverse it without an explicit justification section.
  7. Optional but recommended: run the spec-coherence-check skill (project skill) which sweeps all active proposals for staleness, conflicts, and obsolescence against the current codebase and archived changes. Treat its output as authoritative.
Show full SKILL.md (319 more words)Show less

Pitfalls

  • Trusting an Explore subagent that read only the file-index. The file-index can lag commits by days; for any claim about CURRENT code behaviour, verify against the source tree directly.
  • Misreading grep results: 'rg ToolRendererSlot returns no hits' is technically correct but does NOT imply 'plugin tool-renderer claims do not fire'. The wiring may be inline. Always grep for the FUNCTIONAL identifier (getClaims, forToolName) not just the named component.
  • Skipping the archive sweep because the topic feels new. Topics that already shipped get archived under YYYY-MM-DD-prefixed folder names; ls openspec/changes/archive/ once, costs nothing.
  • Inventing a slot prop contract from memory. Every plugin slot in slot-props.ts requires pluginContext: AnyPluginContext on top of the slot-specific fields. Missing this in a spec is a silent gap.
  • Re-proposing a plugin-based architecture without acknowledging the team chose core built-in (commit 858464d0 for ctx_*). The proposal must explicitly argue why the existing choice should be reversed; otherwise it contradicts shipped reality.
  • Pushing a proposal commit straight to develop without running these checks. develop accumulates contributions quickly; a stale proposal there gets cleaned up by others (which is what happened to openspec/changes/wire-tool-renderer-slot/ in commit e4e63989 — someone deleted my folder upstream, and I had to revert the rest).

Verification

  1. The archive sweep ran and either returned no matches OR I read every matching proposal.md and either align with it (delta-style change) or explicitly argue why a fresh proposal is needed.
  2. For every behaviour claim in the proposal's ## Why section, I have a direct grep / cat result from current code that supports it, not a recollection.
  3. The proposal's ## What Changes section does not contradict any code in packages/client/src/components/tool-renderers/registry.ts, packages/client/src/components/ToolCallStep.tsx, or packages/shared/src/dashboard-plugin/slot-props.ts.
  4. If proposing a new capability name, it does not collide with any folder under openspec/changes/ or openspec/changes/archive/. Specifically: openspec/changes/<name>/ does not exist AND openspec/changes/archive/*-<name>/ does not exist.
  5. openspec validate <change-name> passes (catches structural issues but not contradictions — the above checks catch those).

© BlackBeltTechnology, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in packages/openspec-workflow/.pi/skills/pre-scaffold-openspec-coherence-check of BlackBeltTechnology/pi-agent-dashboard.

Open the folder on GitHubat commit 7a2d171

Compare with similar skills

Pre Scaffold Openspec Coherence Check next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Pre Scaffold Openspec Coherence Check compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Pre Scaffold Openspec Coherence Check this skillBlackBeltTechnology/pi-agent-dashboard315—~1.5kAutomated safety check: PassMIT
Exploration Modefjrevoredo/mini-diarium309—~3.4kAutomated safety check: PassMIT
Python Pep Authorpproenca/dot-skills215—~2.1kAutomated safety check: PassMIT
Cross Critiquewarpdotdev/common-skills610—~1.4kAutomated safety check: PassMIT
Experience UI Bundle 2gp Deployforcedotcom/sf-skills1.1k—~5.5kAutomated safety check: PassApache-2.0
Dsh Find SimplificationsZhou-Yujing114514/deepseek-harness-linux120—~2.6kAutomated safety check: PassMIT

Similar skills

  • Exploration Mode

    fjrevoredo/mini-diarium

    Enter exploration mode: a thinking partner for researching and thinking through ideas and problems before implementation.

    309 GitHub stars~3.4k tokensUpdated yesterday
    Sales & SupportAuto-check passed

  • Python Pep Author

    pproenca/dot-skills

    Drafting Python Enhancement Proposals (PEPs) — proposing a Python language feature, a standard library change, an interoperability standard, or an informational/process document for the Python…

    215 GitHub stars~2.1k tokensUpdated 1 mo ago
    DevelopmentAuto-check passed

  • Cross Critique

    warpdotdev/common-skills

    Run a second round on a contested question by circulating each subagent's independent proposal to the other authors and asking for structured pros and cons, then synthesize.

    610 GitHub stars~1.4k tokensUpdated yesterday
    Sales & SupportAuto-check passed

  • Experience UI Bundle 2gp Deploy

    forcedotcom/sf-skills

    MUST activate when the user wants to package, distribute, or install/upgrade/uninstall/promote a UI Bundle as a Salesforce second-generation (2GP) package (project may contain uiBundles/ or…

    1.1k GitHub stars~5.5k tokensUpdated yesterday
    Sales & SupportAuto-check passed

  • Dsh Find Simplifications

    Zhou-Yujing114514/deepseek-harness-linux

    Find evidence-backed simplifications in DeepSeek Harness code, APIs, configuration, tests, and prose; write or consolidate proposals, identify small inline cleanups, or assess simplifications from…

    120 GitHub stars~2.6k tokensUpdated 4 days ago
    Sales & SupportAuto-check passed

  • Plan Loop

    gaasher/Agent-Loop-Skills

    A skill your agent uses when the user has a coding or engineering prompt and wants it refined into a detailed, executable plan before any code is written — the planning stage of a prompt → plan →…

    174 GitHub stars~2.6k tokensUpdated 3 mo ago
    DevelopmentAuto-check passed

More from BlackBeltTechnology/pi-agent-dashboard

All 70 skills in this repo

  • Browser

    BlackBeltTechnology/pi-agent-dashboard

    Browser automation via the agent-browser CLI. An agent skill from BlackBeltTechnology/pi-agent-dashboard.

    315 GitHub stars~2k tokensUpdated today
    Auto-check passed

  • CI Troubleshoot

    BlackBeltTechnology/pi-agent-dashboard

    Diagnose failed GitHub Actions runs for pi-agent-dashboard: the 11-file workflow taxonomy, affected-test selection, the release pipeline, known failure modes, and how to read gh run logs and…

    315 GitHub stars~3.5k tokensUpdated today
    Auto-check passed

  • Debug Dashboard

    BlackBeltTechnology/pi-agent-dashboard

    Diagnose problems in the running pi-agent-dashboard system: server.log, /api/health, bridge WebSocket connectivity, vitest triage, known-issue FAQ entries.

    315 GitHub stars~1.6k tokensUpdated today
    Auto-check passed

  • Implement

    BlackBeltTechnology/pi-agent-dashboard

    Disciplined implementation in pi-agent-dashboard: the rebuild matrix (extension→reload, server→restart, client→build+restart, openspec-apply→full rebuild) plus the project's code discipline rules.

    315 GitHub stars~2k tokensUpdated today
    Auto-check passed

  • Pi Dashboard

    BlackBeltTechnology/pi-agent-dashboard

    Monitor and control the pi-dashboard server. An agent skill from BlackBeltTechnology/pi-agent-dashboard.

    315 GitHub stars~2.2k tokensUpdated today
    Auto-check passed

  • Session To Guideline

    BlackBeltTechnology/pi-agent-dashboard

    Turn a pi session into a Markdown "how-we-did-it" collaboration guideline: reads the session's JSONL transcript and synthesizes a reusable playbook of which prompts worked, what had to be steered…

    315 GitHub stars~3.2k tokensUpdated today
    Auto-check passed

Categories

Questions about Pre Scaffold Openspec Coherence Check

What does Pre Scaffold Openspec Coherence Check do?

Run before scaffolding any OpenSpec proposal to catch duplicates of archived work and contradictions with shipped architecture. Pre Scaffold Openspec Coherence Check is an agent skill from BlackBeltTechnology/pi-agent-dashboard. Run before scaffolding any OpenSpec proposal to catch duplicates of archived work and contradictions with shipped architecture.

When should I use Pre Scaffold Openspec Coherence Check?

Pre Scaffold Openspec Coherence Check fits situations like: tasks that involve Project scaffolding; tasks that involve Proposals and quotes.

How do I install Pre Scaffold Openspec Coherence Check in Claude Code?

Run `npx skills add BlackBeltTechnology/pi-agent-dashboard --skill pre-scaffold-openspec-coherence-check -a claude-code`. Or copy the skill folder (packages/openspec-workflow/.pi/skills/pre-scaffold-openspec-coherence-check in BlackBeltTechnology/pi-agent-dashboard) into .claude/skills/pre-scaffold-openspec-coherence-check in your project. Claude Code loads it when a task matches its description.

How do I install Pre Scaffold Openspec Coherence Check in Codex?

Run `npx skills add BlackBeltTechnology/pi-agent-dashboard --skill pre-scaffold-openspec-coherence-check -a codex`. Or copy the skill folder (packages/openspec-workflow/.pi/skills/pre-scaffold-openspec-coherence-check in BlackBeltTechnology/pi-agent-dashboard) into .agents/skills/pre-scaffold-openspec-coherence-check in your project. Codex loads it when a task matches its description.

Can I use Pre Scaffold Openspec Coherence Check in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add BlackBeltTechnology/pi-agent-dashboard --skill pre-scaffold-openspec-coherence-check -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/pre-scaffold-openspec-coherence-check, .gemini/skills/pre-scaffold-openspec-coherence-check, .github/skills/pre-scaffold-openspec-coherence-check and .opencode/skills/pre-scaffold-openspec-coherence-check in your project.

What does Pre Scaffold Openspec Coherence Check need to run?

SKILL.md names no scripts, command-line tools or credentials: Pre Scaffold Openspec Coherence Check is instructions for the agent only.

Does Pre Scaffold Openspec Coherence Check access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Pre Scaffold Openspec Coherence Check safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Pre Scaffold Openspec Coherence Check use?

Pre Scaffold Openspec Coherence Check is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Pre Scaffold Openspec Coherence Check use?

About 1.5k tokens (SKILL.md is roughly 6.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Pre Scaffold Openspec Coherence Check?

Skills that share tags, products or a category with Pre Scaffold Openspec Coherence Check: Exploration Mode (fjrevoredo/mini-diarium, 309 stars), Python Pep Author (pproenca/dot-skills, 215 stars), Cross Critique (warpdotdev/common-skills, 610 stars) and Experience UI Bundle 2gp Deploy (forcedotcom/sf-skills, 1.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Pre Scaffold Openspec Coherence Check?

BlackBeltTechnology (a GitHub organization) maintains it in BlackBeltTechnology/pi-agent-dashboard, which has 315 GitHub stars. The repository holds 70 skills in this directory. The repository was last updated on October 10, 2026.

Source: BlackBeltTechnology/pi-agent-dashboard on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.