popoffvg/idea
harness/claude/skills/idea/SKILL.md
This skill should be used when the user says "idea", "I have an idea", "what if we", "we could", "it would be cool if", "feature idea", "improvement idea", or describes a potential feature, improvement, or exploration they want to capture for later.
$ install --global
skillsauthnpx skillsauth add popoffvg/dotfiles ideaInstall 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 20, 2026, 4:38 AM117.2s1 file scanned
SKILL.md
- name:
- idea
- description:
- This skill should be used when the user says "idea", "I have an idea", "what if we", "we could", "it would be cool if", "feature idea", "improvement idea", or describes a potential feature, improvement, or exploration they want to capture for later.
Idea
Capture ideas with full context so they're actionable later.
Usage
/idea <description of the idea>
Procedure
-
Gather context inline (fast, no subagent):
- Repo name:
git rev-parse --show-toplevel | xargs basename - Branch:
git branch --show-current - Recent files:
git diff --name-only HEAD~3..HEAD 2>/dev/null
- Repo name:
-
Spawn context-keeper agent (haiku model) with this prompt:
Save an idea to memory. Use `memory_save` with type=`task` and the following content:
## <Idea title, 5-10 words> — <date>
**Context:** <repo> / <branch>
**Related files:** <recently changed files, if relevant>
<1-2 paragraphs expanding the idea: what it solves, rough approach, constraints>
### Open questions
- <Things to figure out before implementing>
---
Idea text: <user's idea>
Repo: <repo>
Branch: <branch>
Recent files: <files>
The agent must:
- First call
memory_contextto check for duplicate ideas - Then call
memory_savewith the formatted content
-
Also write the idea to
~/ctx/insights/_ideas/<slug>.md(slug: lowercase, hyphens, max 60 chars) as a file backup. -
Report the saved path and a one-line summary to the user.
Rules
- Use context-keeper agent (haiku) for memory operations — never call MCP tools directly
- One idea per invocation — if the user gives multiple, spawn parallel agents
- Dedup — the agent checks memory before saving; if a match exists, it appends instead
Related Skills
popoffvg/improve-claude-local
tools
VerifiedTrustedCommunity
Improve a whole CLAUDE.local.md — the private, per-project rules captured from user corrections. Wraps each conditional rule in a <task-relevant> block so it only surfaces for matching work, merges duplicates, generalizes one-off facts, drops stale entries, and routes raw project facts to engram. Use when the user says "improve claude.local", "clean up the local rules", "claude.local is bloated", or after the Stop hook has appended many rules.
2SKILL.mdUpdated Jun 25, 2026
popoffvg/workflow
testing
VerifiedTrustedCommunity
WM pipeline and conventions shared across all phases. Agents must read this before spec, impl, or verify work.
2SKILL.mdUpdated Jun 19, 2026
popoffvg/code
development
VerifiedTrustedCommunity
One entry point for spec writing, implementation, and bug fixing. Default is new (write spec → grill loop → produce notes → author TODO bodies). Other subcommands: verify (audit), revise (sync to shipped), prototype (settle a decision), code-map (diagram), impl (execute one TODO), fix (analyze cause, correct thoughts, fix behavior), help (this page). Invoke as /code <subcommand>.
2SKILL.mdUpdated Jun 19, 2026
popoffvg/red-green-refactor
development
VerifiedTrustedCommunity
Red-Green-Refactor cycle for bug fixes. Before fixing a bug, first write a failing test that reproduces it (Red), then make the minimal change to pass (Green), then clean up the code (Refactor). Use on any bug fix, error correction, failing test repair, or when user says "fix this bug".
2SKILL.mdUpdated Jun 18, 2026