Loading...
Loading...
Found 102 Skills
Groove.cm platform help — GroovePages, GrooveFunnels, GrooveSell, GrooveMail, GrooveAffiliate, GrooveMember, GrooveVideo, GrooveWebinar, GrooveBlog, GrooveKart, GrooveProof. Use when asking 'how do I do X in Groove', configuring Groove modules, setting up GrooveMail automation, GrooveSell checkout, GrooveAffiliate commissions, GrooveMember courses, or GrooveWebinar events. Do NOT use for general funnel strategy (use /sales-funnel), general email marketing strategy (use /sales-email-marketing), general affiliate program design (use /sales-affiliate-program), general webinar strategy (use /sales-webinar), general membership strategy (use /sales-membership), or general checkout optimization (use /sales-checkout).
Create or update .groove/index.md config interactively. Run before groove install.
Check memory backend health and configuration.
Write the daily memory log entry. Use at end of day to record what happened.
Install groove backends, companions, and AGENTS.md bootstrap. Run once per repo.
Start the workday: review yesterday, create today's daily memory, load tasks, prepare agenda. Use when beginning the day.
Configure task backend settings interactively.
Roll up the weekly memory log from daily entries.
Install groove's Claude Code native shell hooks into .claude/settings.json. Enables deterministic session-end reminders, git activity capture, and managed-path protection.
Pull latest groove skills and apply pending migrations to local groove state.
Publish a workflow learning to the groovebook shared commons as a GitHub PR. Use after groove-work-compound when a learning is worth sharing.
Daily/weekly/monthly/git log population and session context management. Use when: (1) writing daily closeout log; (2) rolling up weekly/monthly memory; (3) recording git summary; (4) starting/ending sessions; (5) creating specs or docs. NOT for: task management (use task); compound loop (use work).