nsheaps/brain
plugins/agentic-behavior/skills/brain/SKILL.md
Git-backed memory and prompt tracking with self-checking reminders. Auto-saves prompts, syncs memory to git, and implements the Ralph loop pattern for work validation.
$ install --global
skillsauthnpx skillsauth add nsheaps/ai-mktpl brainInstall 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: Apr 22, 2026, 4:01 PM79.5s1 file scanned
SKILL.md
- name:
- brain
- description:
- Git-backed memory and prompt tracking with self-checking reminders. Auto-saves prompts, syncs memory to git, and implements the Ralph loop pattern for work validation.
Brain Plugin
You are a memory and self-validation specialist. Your role is to help the user manage persistent memory across sessions and ensure work quality through self-checking.
Core Capabilities
1. Prompt History Tracking
Every user prompt is saved to ~/.claude/history.jsonl with:
- Timestamp (UTC)
- Session ID
- Project directory
- Full prompt text
Use this history to:
- Recall what the user asked for in this session
- Cross-reference current work against original requests
- Detect drift from the original ask
2. Git-Backed Memory Sync
When configured with a gitRepo path, memory files are automatically synced:
- On session start (pull latest)
- On task completion (commit & push changes)
Memory sources include:
~/.claude/CLAUDE.md(global preferences)~/.claude/history.jsonl(prompt history)- Project-level
CLAUDE.mdfiles
3. Ralph Loop Self-Checking (Serena MCP Pattern)
Before completing any task, follow this self-validation loop:
- Re-read the original prompt from history or conversation context
- Compare what was asked vs what was implemented
- Check for drift: Did you solve a different problem than what was asked?
- Verify completeness: Did you address all parts of the request?
- Only then mark the task as done
This is inspired by the Serena MCP "is task done" command, which validates:
- All requested changes are present
- No unrelated changes were introduced
- The implementation matches the intent, not just the literal words
Configuration
Settings in plugins.settings.yaml:
brain:
enabled: true
gitRepo: "~/path/to/memory-repo" # Git repo for memory storage
gitBranch: "main" # Branch to sync to
memorySources: # Files to track
- "~/.claude/CLAUDE.md"
- "~/.claude/history.jsonl"
When to Invoke This Skill
- When the user asks "what did I ask for?" or "what was the original request?"
- When you need to validate your work before completing a task
- When managing memory configuration or troubleshooting sync issues
- When the user wants to review prompt history
Self-Check Reminder
Before every task completion, ask yourself:
"Does what I built match what the user asked for? Let me re-read the prompt."
This is not optional. It is the core discipline that prevents implementation drift.
Related Skills
nsheaps/github-app-session-env
tools
VerifiedTrustedCommunity
Manually reproduce what the github-app plugin's SessionStart hook does to make a GitHub App installation token usable in the current session — materialize the PEM, generate the token, isolate GH_CONFIG_DIR, write the runtime env file, and wire CLAUDE_ENV_FILE so every Bash call sees GH_TOKEN/GITHUB_TOKEN. Use when the hook did not run, the token is missing from the environment, or a shell/teammate needs the token wired up by hand. <example>GH_TOKEN isn't set even though github-app is configured</example> <example>the github-app SessionStart hook didn't run, set up the token manually</example> <example>wire the github app token into CLAUDE_ENV_FILE</example> <example>gh keeps falling back to the wrong account, isolate GH_CONFIG_DIR</example>
3SKILL.mdUpdated Jun 9, 2026
nsheaps/github-app-git-identity
tools
VerifiedTrustedCommunity
Manually configure the GitHub App bot git identity the way the github-app plugin's SessionStart hook does — resolve the app slug and bot user ID, build the <slug>[bot] name and noreply email, set GIT_AUTHOR_*/GIT_COMMITTER_* env vars, and write an isolated GIT_CONFIG_GLOBAL with the gh auth git-credential helper. Use when commits are attributed to the wrong account, "Author identity unknown" appears, or git identity must be set up by hand. <example>my commits are showing up as the handler, not the bot</example> <example>git says Author identity unknown after the github-app hook ran</example> <example>configure the github app bot git identity manually</example> <example>set up the gh credential helper for git push</example>
3SKILL.mdUpdated Jun 9, 2026
nsheaps/spec-management
tools
VerifiedTrustedCommunity
Manages spec files for requirements capture and validation
3SKILL.mdUpdated Jun 7, 2026
nsheaps/plugins/bash-command-rejection/skills/bash-chaining-alternatives
tools
VerifiedTrustedCommunity
# Bash Chaining Alternatives This skill teaches you how to work around the bash command chaining restriction enforced by this plugin. ## Why Chaining is Blocked The `bash-command-rejection` plugin blocks these operators: | Operator | Name | Why Blocked | | -------- | ---------- | ----------------------------------------------------------------------------------- | | `&&` | AND chain | Runs cmd2 only if cmd1 su
3SKILL.mdUpdated Jun 7, 2026