deathbyknowledge/gsv-context-and-skills
skills/gsv-context-and-skills/SKILL.md
Guide on how context and skills work in GSV and how to add/edit them.
$ install --global
skillsauthnpx skillsauth add deathbyknowledge/gsv gsv-context-and-skillsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 28, 2026, 2:41 AM131.4s1 file scanned
SKILL.md
- name:
- gsv-context-and-skills
- description:
- Guide on how context and skills work in GSV and how to add/edit them.
GSV Context and Skills
Prompt Assembly
GSV assembles process context from explicit, inspectable sources:
- Profile context from
config/ai/profile/{profile}/context.d/*.mdor a user profile under~/profiles.d/{profile}/context.d/*.md. - Home context from
~/context.d/*.md. - A compact index of available skills from layered
skills.ddirectories. - Process context supplied by the current assignment or runtime.
The skill index contains ids and descriptions only. It does not include full bodies or long source paths.
Tool and integration metadata is not the same thing as prompt context. The outer chat tool list may show only generic tools such as Shell, Read, and CodeMode, while connected MCP servers are mounted inside CodeMode as mcpTools metadata and generated async functions. Do not conclude that an MCP server is unavailable just because there is no top-level tool namespace for it.
Skill Commands
Use the native shell:
skills list
skills search <query>
skills show <skill>
skills files <skill>
skills read <skill> <file>
Read skills show <skill> before relying on a workflow. Use skills files and skills read for supporting references, templates, or examples.
Where Information Belongs
config/ai/profile/{profile}/context.d/*.md: short operator-managed role and runtime guidance.~/profiles.d/{profile}/context.d/*.md: user-authored worker profile specialization, available through spawn and schedules.~/context.d/*.md: concise user-global standing context useful to most processes.~/skills.d/: reusable user-level process workflows./src/packages/{package}/skills.d/: workflows shipped by visible package source.~/knowledge/: durable searchable reference material, not always-loaded prompt context.- Explicit project files or repositories: task-local continuity, decisions, open loops, and handoff state.
- Process assignment context: current task instructions, temporary handoff notes, and files attached to a spawned process.
Repo-root skills/ in root/gsv is only a distribution source. Bootstrap copies those files into user ~/skills.d/ when missing. Runtime processes read layered skills.d, not repo-root skills/ directly.
Editing Rules
- Read the current file before editing.
- Keep context files short and curated.
- Put reusable procedures in skills, not profile or home context.
- Put raw reference material in knowledge or a skill reference file, not always-loaded context.
- Preserve user-authored structure and do not overwrite local skills just because a seeded source exists.
- After a repeated correction or reusable workflow, update the relevant writable skill source.
Package skills follow package source rules. Edits under /src/packages/<package>/skills.d are staged until pkg source commit.
Related Skills
deathbyknowledge/browser-shell
development
VerifiedTrustedCommunity
Use active GSV web shell browser targets to inspect windows/apps, run browser JS, open files, and move files across targets.
58SKILL.mdUpdated May 25, 2026
deathbyknowledge/gsv-process-identity
documentation
VerifiedTrustedCommunity
Guide on what a GSV process is, how to orient around its identity, cwd, virtual filesystem paths, source mounts, and runtime events.
58SKILL.mdUpdated May 6, 2026
deathbyknowledge/gsv-process-coordination
documentation
VerifiedTrustedCommunity
Guide on how to coordinate durable GSV processes, including spawning, IPC, handoffs, scheduled work, conversation state, and compaction.
58SKILL.mdUpdated May 6, 2026
deathbyknowledge/gsv-system-operations
testing
VerifiedTrustedCommunity
Guide on how to operate and update a GSV deployment, including which layer changed, what to validate, and what to deploy or sync.
55SKILL.mdUpdated May 6, 2026