plugins/word-vomit/skills/word-vomit/SKILL.md
Use when the user wants to dump unstructured thoughts, ideas, or notes that need to be organized. Triggers: "brain dump", "word vomit", "let me think out loud", "process my notes", "organize my thoughts", "dump my ideas".
npx skillsauth add nsheaps/ai-mktpl word-vomitInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Process unstructured user thoughts into organized, actionable items.
If the user hasn't already written their thoughts to a file, save them to:
.claude/scratch/word-vomit-<date>.md
Add the marker at the top of the file:
<!-- word-vomit -->
# Brain Dump — <date>
- thought 1
- thought 2
...
For each item in the file:
| Category | Destination | Labels |
| ----------------- | ---------------------------- | ------------- |
| Bug | GitHub issue | bug |
| Task | GitHub issue or TaskCreate | none |
| Feature idea | GitHub issue | enhancement |
| Research question | GitHub issue | research |
| Decision needed | Present to user with options | none |
| Observation/note | Append to relevant doc | none |
| Reminder | TaskCreate with context | none |
| Duplicate | Link to existing issue | none |
gh issue list before creating new onesAfter filing each item, update the original file:
# Before
- fix the auth endpoint returning 500
# After
- ~~fix the auth endpoint returning 500~~ → [nsheaps/agent-team#42](https://github.com/nsheaps/agent-team/issues/42)
Rules:
~~text~~Provide a structured summary:
## Processed Items
| # | Original | Category | Filed As | Priority |
| --- | --------------- | -------- | --------------- | -------- |
| 1 | "fix auth 500" | Bug | nsheaps/repo#42 | p1 |
| 2 | "add dark mode" | Feature | nsheaps/repo#43 | p3 |
## Decisions Needed
- Redis vs Memcached — need user input on requirements
needs-clarification labeltools
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>
tools
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>
tools
Manages spec files for requirements capture and validation
tools
# 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