Skip to content

dev-tools: genericise Basalt Cortex references in public skills - #76

Open
marcusjezweb wants to merge 1 commit into
mainfrom
cortex-ref-cleanup
Open

dev-tools: genericise Basalt Cortex references in public skills#76
marcusjezweb wants to merge 1 commit into
mainfrom
cortex-ref-cleanup

Conversation

@marcusjezweb

Copy link
Copy Markdown
Collaborator

Summary

Two public skills in plugins/dev-tools/ hardcoded ~/Documents/basalt-cortex/ as a knowledge-vault location. This leaked internal Jezweb setup into a skill used by external contributors — most users don't have that directory. Basalt Cortex is also now retired internally (shared-knowledge role moved to .jez/knowledge/ per 2026-04-22 team decision; private mining plugin removed from team-skills in 07eafb0).

Reworded to generic "personal knowledge vault if you keep one" framing across three files.

Changes

  • plugins/dev-tools/skills/deep-research/SKILL.md (Step 2): swap "Basalt Cortex" bullet for generic "personal knowledge store (Obsidian vault, ~/Documents/notes/, a private repo of markdown files)". Keep the useful grep -rl KEYWORD pattern.
  • plugins/dev-tools/skills/deep-research/SKILL.md (Step 7): drop "Basalt Cortex project" proper noun from the Cloudflare-capabilities anecdote; keep the substantive "Workers AI toMarkdown, Vectorize metadata filtering, D1 FTS5" examples. The point about Claude training data being behind on platform features lands without needing the internal project reference.
  • plugins/dev-tools/skills/team-update/SKILL.md (Knowledge row): generic personal-vault pattern instead of hardcoded Basalt Cortex.
  • plugins/dev-tools/skills/team-update/references/discovery-patterns.md: same two-location cleanup (table row + "what to capture" bullet).

Test plan

  • All three files edited, no syntactic breakage in markdown
  • grep confirms no remaining "basalt" or "cortex" references in plugins/dev-tools/
  • Skills still read coherently without the proper-noun anchor

Context

Raised per Jez greenlight in Dev Chat (msg nP6g6buoQSY) following my flag yesterday about three stale public-facing Cortex refs. Sister commit in team-skills was 07eafb0 (removed the basalt plugin entirely). A further audit-fix.py stale-ref cleanup exists in .jez/scripts/ but is internal tooling and scoped for a separate pass.

🤖 Generated with Claude Code

Both deep-research and team-update skills hardcoded
~/Documents/basalt-cortex/ as a knowledge-vault location. This leaked
internal Jezweb setup into a public skill — most users don't have that
directory. Basalt Cortex is also now retired internally (the shared-
knowledge role moved to .jez/knowledge/ per 2026-04-22 team decision).

Reworded to generic "personal knowledge vault if you keep one" framing:
- deep-research/SKILL.md Step 2: point at Obsidian/Documents/notes/
  generically, keep the grep-for-KEYWORD pattern as the useful bit
- deep-research/SKILL.md Step 7: drop "Basalt Cortex project" proper
  noun from the Cloudflare-capabilities anecdote, keep the substantive
  "Workers AI toMarkdown, Vectorize metadata filtering, D1 FTS5" detail
- team-update/SKILL.md Knowledge row: generic personal-vault pattern
- team-update/references/discovery-patterns.md: same

Closes internal follow-up on basalt plugin removal (team-skills 07eafb0).
Raised per Jez greenlight in Dev Chat (msg nP6g6buoQSY).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant