mauroporras/misc-configs/claude/skills/07-guess-whats-next
misc-configs/claude/skills/07-guess-whats-next/SKILL.md
--- disable-model-invocation: true argument-hint: [hint] allowed-tools: Read --- # Guess What's Next Based on the current conversation, try to predict what the user is about to ask or work on next. ## Hint If $ARGUMENTS is non-empty, treat it as a steering signal: - Bias your ranking and the kinds of guesses you generate toward it (e.g. a hint about "tests" should push test-related predictions higher). - It narrows the area to think about but doesn't override the conversation. - If the hint
$ install --global
skillsauthnpx skillsauth add mauroporras/dotfiles misc-configs/claude/skills/07-guess-whats-nextInstall 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 14, 2026, 3:06 AM116.8s1 file scanned
SKILL.md
- disable-model-invocation:
- true
- argument-hint:
- [hint]
- allowed-tools:
- Read
Guess What's Next
Based on the current conversation, try to predict what the user is about to ask or work on next.
Hint
If $ARGUMENTS is non-empty, treat it as a steering signal:
- Bias your ranking and the kinds of guesses you generate toward it (e.g. a hint about "tests" should push test-related predictions higher).
- It narrows the area to think about but doesn't override the conversation.
- If the hint contradicts what the conversation suggests, still produce guesses, but call out the tension briefly.
If $ARGUMENTS is empty, ignore this section and use the conversation alone.
What to Analyze
Base your guesses entirely on the current conversation (and $ARGUMENTS, if provided):
- Trajectory: What has the user been building toward? What's the logical next step?
- Unfinished threads: Did they mention something earlier that hasn't been addressed yet?
- Patterns: Are they iterating on a theme (e.g., tweaking configs one by one)?
- Loose ends: Did a previous answer raise a follow-up they haven't asked yet?
- Implicit needs: What would naturally come after the work they just did?
Do NOT run Git commands, grep the codebase, or investigate anything outside the conversation. This is purely a reading-the-room exercise.
Presenting Your Guesses
Present 3 guesses ranked by confidence:
1. [N%] <Your top guess>
Why: <brief explanation of what led you here>
2. [N%] <Second guess>
Why: <brief explanation>
3. [N%] <Wild card guess>
Why: <brief explanation or just a hunch>
Related Skills
mauroporras/misc-configs/claude/skills/custom-branch-changes-analyze
tools
VerifiedTrustedCommunity
--- disable-model-invocation: true allowed-tools: Read, Bash(git --no-pager log:*), Bash(git --no-pager diff:*) --- # Get familiar with the current branch's changes ## Context - Commits on this branch: !`git --no-pager log origin/HEAD..HEAD --oneline` - List of changed files: !`git --no-pager diff origin/HEAD...HEAD --stat` - Full diff: !`git --no-pager diff origin/HEAD...HEAD` ## Your task Analyze the changes purely based on the code (do not check the branch name, linked GitHub issues, PR
3SKILL.mdUpdated May 30, 2026
mauroporras/misc-configs/claude/skills/custom-staged-commit
tools
VerifiedTrustedCommunity
--- disable-model-invocation: true context: fork argument-hint: [push] [issue-number] allowed-tools: Bash(git --no-pager diff:*), Bash(git rev-parse:*), Bash(git remote get-url:*), Bash(git commit:*), Bash(git push:*) model: haiku --- # Commit STAGED changes, optionally push ## Context - Current staged changes only: !`git --no-pager diff --staged` - Current branch: !`git rev-parse --abbrev-ref HEAD` - Remote URL: !`git remote get-url origin` - Arguments (issue number and/or `push`, empty if n
3SKILL.mdUpdated May 29, 2026
mauroporras/misc-configs/claude/skills/custom-unresolved-pr-comments-summarize
tools
VerifiedTrustedCommunity
--- disable-model-invocation: true allowed-tools: Write, Bash(gh:*) --- # Fetch and summarize this PR's UNRESOLVED comments ## Context - OWNER: !`gh repo view --json owner -q .owner.login` - REPO: !`gh repo view --json name -q .name` - PR_NUMBER: !`gh pr view --json number -q .number` ## Your task ### Step 1: Fetch unresolved inline review threads Use this GraphQL query (substitute OWNER, REPO, PR_NUMBER from context above): ```bash gh api graphql -f query=' query($owner: String!, $repo:
3SKILL.mdUpdated May 27, 2026
mauroporras/misc-configs/claude/skills/custom-staged-summarize
tools
VerifiedTrustedCommunity
--- disable-model-invocation: true allowed-tools: Read, Bash(git --no-pager diff:*) model: haiku --- # Summarize STAGED changes ## Context - Current staged changes only: !`git --no-pager diff --staged` ## Your task Summarize the changes purely based on the code (do not check the branch name, linked GitHub issues, PR descriptions, or any other contextual clues). REQUIRED: - Prioritize brevity over grammar: Keep messages short, even if grammatically imperfect NEVER: - Run additional Git
3SKILL.mdUpdated May 27, 2026