Add per-target target_naming setting that controls how skill directories
are named in sync targets. 'flat' (default) preserves the existing
flattened __ separator behavior. 'standard' uses the SKILL.md name field
directly, following the Agent Skills specification.
Standard mode:
- Validates SKILL.md names match directory basenames
- Detects and skips name collisions with warnings
- Auto-migrates managed entries when switching from flat to standard
- Preserves legacy entries when bare name is already occupied
Also includes:
- Per-target toggle via CLI (--target-naming), TUI (N key), and Web UI
- Collision output redesigned as deduplicated compact summary
- Config inheritance: global target_naming → per-target override
- JSON schema + UI validation for the new field
Closes#110
- registry.yaml now lives in skills/ dir (synced via git)
- Updated file-structure, declarative-manifest, appendix, init docs
- Added migration note for v0.19+ users
Add the new metadata: block placement for targets, explain the
priority rule (metadata wins over top-level), and describe the
metadata block as an ecosystem convention.
Add comprehensive skill design patterns page covering five structural
templates (Tool Wrapper, Generator, Reviewer, Inversion, Pipeline) with
a decision flowchart, use-case categories, and detailed examples.
Update `new` command reference with -P/--pattern flag documentation and
a scaffold directories table. Cross-link from skill-design.md.
Detect inline API keys, tokens, and passwords in skill files via 10 new
hardcoded-secret-* rules (HIGH severity): Google API keys, AWS access
keys, GitHub PATs (classic + fine-grained), Slack tokens, OpenAI keys,
Anthropic keys, Stripe keys, PEM private key blocks, and generic
api_key/password assignments.
Closes a gap where GitHub Secret Scanning caught a Google API key in a
skill file but our audit engine missed it entirely.
Improve all 5 active skills with pushy descriptions for better
triggering accuracy, following devcontainer as the gold standard.
- changelog: add trigger scenarios (release notes, version prep)
- cli-e2e-test: add trigger scenarios (runbook, E2E validation)
- codebase-audit: add 3 new audit dimensions (handler split, oplog
coverage, web API consistency) and trigger scenarios
- implement-feature: add project patterns reference (handler split,
dual-mode, TUI, web API, oplog) and trigger scenarios
- update-docs: expand scope to all 7 doc categories with code-to-doc
mapping guide and trigger scenarios
Also remove empty .skillshare/skills/frontend/ directory.
The 1294-line audit.md mixed command reference, conceptual teaching,
rule management, and CI/CD recipes. Split into:
- understand/audit-engine.md — threat model, detection rules, risk
scoring, command tiering, cross-skill analysis
- reference/commands/audit-rules.md — rule management, custom rules,
built-in rule IDs table (adds 4 cross-skill finding IDs)
- how-to/recipes/ci-cd-skill-validation.md — absorb output format
docs (SARIF, Markdown, JSON+jq, exit codes)
- reference/commands/audit.md — slim to ~370 lines, link to new pages
Also fixes:
- Replace ghost rule `system-writes-0` with `insecure-http-0` in all
docs (the old ID no longer exists in rules.yaml)
- Update 3 cross-page links in security.md
- Update 1 rule ID in configuration.md
- Add sidebar entries for both new pages
Covers 13 test scenarios for dotfiles manager symlink support:
symlinked source/target, chained symlinks, merge/copy modes,
status/diff/list/collect through symlinks, and idempotency.
Vercel skills issue #386 (8 commenters) confirms this is the #1 pain point
for enterprise users — their update/check is hardcoded to GitHub Trees API.
Skillshare uses local git operations, working with any remote out of the box.