knoopx/workspace-docs
agent/skills/knowledge/workspace-docs/SKILL.md
Check workspace for problem specs and convention docs before writing code. Use when starting implementation tasks, fixing tests, or any code change to find format rules and constraints.
$ install --global
skillsauthnpx skillsauth add knoopx/pi workspace-docsInstall 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 18, 2026, 6:38 AM61.0s1 file scanned
SKILL.md
- name:
- workspace-docs
- description:
- Check workspace for problem specs and convention docs before writing code. Use when starting implementation tasks, fixing tests, or any code change to find format rules and constraints.
- topic:
- Workspace Documentation
- token_cost:
- 140
- requires_tools:
- [read, find]
When to use
Before writing code for a non-trivial task, check if the workspace has a problem specification or convention document.
Rules
- These are cheap to read and often contain the exact format rules, edge cases, or constraints the tests assert
- Look for (in priority order):
.docs/instructions.mdand.docs/instructions.append.md(exercism-style problem specs) - Also check:
AGENTS.md/CLAUDE.md(agent-specific instructions at repo root) - Also check:
README.mdin the current directory,SPEC.md/SPECIFICATION.md, anddocs/*.md - Use find to discover them (
*.md,.docs/*.md,AGENTS.md) and read the relevant one - Do this ONCE at the start of a task, not every turn
- If the spec disambiguates a failing test, that single read saves many debug iterations
- Skip for pure read-only questions — only invest the Read call when you are about to change code
- NEVER skip this step when about to write code — the spec often contains test constraints
File locations
.docs/instructions.md, .docs/instructions.append.md, AGENTS.md, CLAUDE.md, README.md, SPEC.md, SPECIFICATION.md, docs/*.md.
Example
Before coding: find(".docs/*.md") → finds instructions.md → read(".docs/instructions.md") reveals test constraints like "output must be sorted". Saves multiple debug iterations.
Related Skills
knoopx/notify
tools
VerifiedTrustedCommunity
Inform the user what is happening — skip passive lookups
52SKILL.mdUpdated May 20, 2026
knoopx/markdown-rendering
development
VerifiedTrustedCommunity
Renders markdown to self-contained HTML with a custom dark stylesheet and opens in browser. Use when previewing markdown documents, generating styled HTML from README or report files.
52SKILL.mdUpdated May 20, 2026
knoopx/jj-hunk
testing
VerifiedTrustedCommunity
Programmatic hunk selection for Jujutsu — split, commit, or squash specific hunks without interactive prompts. Use when making partial commits or selective squashes.
52SKILL.mdUpdated May 18, 2026
knoopx/jj-core
content-media
VerifiedTrustedCommunity
Manage version control with Jujutsu (jj) — no staging area, immediate changes, smart rebasing. Use when navigating history, squashing, or pushing to Git remotes.
52SKILL.mdUpdated May 18, 2026