SKILLS/next-step/SKILL.md
Analyzes album state and recommends the optimal next action. Use when the user asks "what should I do next?" or "what's left to do?"
npx skillsauth add pinkpixel-dev/skills-collection-2 next-stepInstall 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.
Input: $ARGUMENTS (optional album name)
Analyze current project state and recommend the single best next action.
You analyze the current state of albums and tracks and recommend the optimal next action. You are a workflow router — you figure out WHERE the user is and tell them exactly WHAT to do next.
get_session() — check last_album from session contextget_album_progress(album_slug) to analyze itlist_albums() to find all albums, then get_album_progress() on each to pick the most actionablefind_album(name) — fuzzy match by name, slug, or partialget_album_progress(album_slug) — get status, phase, track countsAnalyze album and track statuses to determine the optimal next action:
Album Status = "Concept"
→ "Define the album concept. Run the 7 Planning Phases with /bitwize-music:album-conceptualizer"
Album Status = "Research Complete"
→ Any tracks Sources Pending?
YES → "Sources need verification. Review SOURCES.md and verify each source."
NO → "Ready to write! Pick a track and use /bitwize-music:lyric-writer"
Album has tracks with status "Not Started"
→ "Write lyrics for track [first not-started track]. Use /bitwize-music:lyric-writer"
Album has tracks with status "In Progress" (lyrics partially written)
→ "Finish lyrics for track [first in-progress track]. Use /bitwize-music:lyric-writer"
Album has tracks with status "Sources Pending"
→ "Verify sources for track [name]. Check SOURCES.md, then update sources_verified field."
All tracks have lyrics, none generated
→ "All lyrics complete! Style prompts should be ready. Run /bitwize-music:pronunciation-specialist to check for pronunciation risks, then /bitwize-music:lyric-reviewer for final QC, then /bitwize-music:pre-generation-check to validate all gates before generating on Suno."
Some tracks generated, some not
→ "Generate track [first un-generated track] on Suno. Use /bitwize-music:suno-engineer"
All tracks generated
→ "All tracks generated! Import audio with /bitwize-music:import-audio, then master with /bitwize-music:mastering-engineer"
Album Status = "Complete"
→ "Album is complete! Release with /bitwize-music:release-director"
Album Status = "Released"
→ "This album is released! Consider promotional content with /bitwize-music:promo-director"
→ Also suggest: "Start a new album? Check your ideas with /bitwize-music:album-ideas list"
NEXT STEP
=========
Album: [name] ([genre]) — [status]
Progress: [X/Y tracks complete]
RECOMMENDED ACTION:
[Clear, specific instruction with skill name]
WHY:
[One sentence explaining why this is the right next step]
AFTER THAT:
[Brief mention of what comes after this step]
If no album specified and multiple exist:
NEXT STEP
=========
You have X albums. Here's the most actionable:
PRIORITY 1: [album-name] ([genre])
Status: [status] | Progress: [X/Y tracks]
→ [Recommended action]
Also in progress:
- [album-2] — [brief status]
- [album-3] — [brief status]
Or start something new:
- /bitwize-music:album-ideas list (X ideas pending)
- /bitwize-music:new-album
When multiple albums are in progress, prioritize:
tools
Perform lateral movement across Windows networks using WMI-based remote execution techniques including Impacket wmiexec.py, CrackMapExec, and native WMI commands for stealthy post-exploitation during red team engagements.
data-ai
Detects lateral movement techniques including Pass-the-Hash, PsExec, WMI execution, RDP pivoting, and SMB-based spreading using SIEM correlation of Windows event logs, network flow data, and endpoint telemetry mapped to MITRE ATT&CK Lateral Movement (TA0008) techniques.
tools
Kubernetes penetration testing systematically evaluates cluster security by simulating attacker techniques against the API server, kubelet, etcd, pods, RBAC, network policies, and secrets. Using tools
testing
Assess the security posture of Kubernetes etcd clusters by evaluating encryption at rest, TLS configuration, access controls, backup encryption, and network isolation.