Fix skills.json determinism (CI blocker) and upgrade the playground
The check-generated CI step was failing with "web/skills.json is stale" because build-skills.mjs stamped a wall-clock generatedAt into the file, so every rebuild differed and git diff --exit-code never matched. - web/build-skills.mjs: drop the unused generatedAt timestamp -> deterministic output the CI staleness check can verify. Also tags each skill with its tier. - skill-tiers.json: single machine-readable source for tier membership (Production-Ready / Experimental); TIERS.md points to it. Playground upgrades (hosted on GitHub Pages): - Tier filter (Production-Ready / Stable / Experimental) + per-tile tier badges. - "Use this skill in another tool" panel: copy the instructions formatted for ChatGPT, Gemini, or raw — mirrors the generated exports/ files. - web/README documents the new options and the deterministic build. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_016JWn5jRD5tcEFKrubjQ6Px
This commit is contained in:
@@ -0,0 +1,19 @@
|
||||
{
|
||||
"_comment": "Machine-readable source for skill tiers. Keep in sync with TIERS.md. Any skill not listed here is 'stable'. Consumed by web/build-skills.mjs to tag skills.json.",
|
||||
"productionReady": [
|
||||
"prd-template", "meeting-notes", "stakeholder-update", "user-research-synthesis", "competitive-analysis",
|
||||
"rice-prioritisation", "feature-prioritisation", "okr-builder", "roadmap-narrative", "rice-impact-matrix",
|
||||
"sprint-planning", "sprint-brief", "user-story-writer", "retro-analysis", "ab-test-planner", "product-launch-checklist", "technical-spec-template",
|
||||
"customer-journey-map", "assumption-mapper", "user-interview-synthesis", "discovery-interview-guide", "job-story-mapper",
|
||||
"data-analysis-standard", "retention-analysis", "cohort-analysis", "metrics-framework", "product-health-analysis",
|
||||
"cs-health-scorecard", "churn-analysis", "qbr-deck", "renewal-playbook", "customer-success-plan", "cs-escalation-brief",
|
||||
"code-review-checklist", "incident-postmortem", "architecture-decision-record", "api-docs-writer", "runbook-writer", "changelog-generator", "pr-description-writer", "technical-debt-register",
|
||||
"go-to-market", "competitor-teardown", "product-positioning-doc",
|
||||
"executive-summary", "press-release"
|
||||
],
|
||||
"experimental": [
|
||||
"instagram-post-downloader", "substack-notes-scraper", "thumbnail-creator", "notebooklm-connector",
|
||||
"email-triage", "morning-intelligence", "last-30-days-research", "competitor-signal-tracker",
|
||||
"multi-source-signal-synthesiser"
|
||||
]
|
||||
}
|
||||
Reference in New Issue
Block a user