This skill should be used when the user wants to build, prototype, or reshape an app, tool, CLI, API, automation, workflow, requirements document, knowledge tree, policy, curriculum, argument outline, or other evaluable artifact before architecture. Responds to "let's build", "prototype this", "surface first", "SFD", "click dummy", "derive contracts", "docket contracts", "requirements as surface", "knowledge tree", "policy surface", or any request describing what should exist without specifying internals.
This skill should be used when the user wants to create music with Suno (AI music generation) — a song, track, beat, anthem, jingle, or instrumental — or wants to execute an existing suno-pack for real via the suno-pp-cli integration — rendering packs into actual tracks, cover pipelines, Suno library checks, one-roll experiment lanes, and saga-synced field journals. Produces a complete track package — concept document, per-version style and lyrics prompts, instrumental variants, cover workflow, runnable scripts, and an experiments lane book. Supports "--versions 5.5 4.5" and "--mode experimental". Responds to "suno-pack", "make a track in Suno", "write me a song", "Suno prompt", "lyrics for Suno", "instrumental version", "render the pack", "make it real", "generate it for real", "run the cover pipeline", "how are my Suno tracks doing", "suno experiment", "sync the journal", "rebuild the experiment saga", or any request to turn an idea, mood, or theme into Suno-ready prompts or finished Suno tracks.
This skill should be used when the user wants to know what the collective brain — social media (X/Twitter and Reddit), GitHub, the web, or research papers — is saying, building, or publishing about a topic — trends, sentiment, hot takes, trending repos, paper-vs-practitioner checks. Also runs recurring sweeps saved as configs. Responds to "ask the hivemind", "what's the hot shit in", "what does social media say", "what does reddit/twitter/X think", "what are people saying about", "check the socials", "--radar", "trending repos and what is X saying about them", "which repos get the most mentions", "what does the research say — and do practitioners agree", "repeat <slug>", "wiederhole den Sweep", "freeze this process", "frier den Prozess ein", or any question whose best answer lives in threads, comments, replies, repos, and preprints rather than articles. NOT for single-item lookups ("find me a paper on X", "search the web for Y") — use search/research skills. Read-only research — never posts.
This skill should be used at session start, when entering a new project, or when the user says 'wake up', 'load memory', 'boot', 'memory-boot'. Assembles identity, procedural knowledge, project context, and recent session state into a boot packet from the agent's vault.
This skill should be used when the agent needs to save something to memory — observations, lessons, decisions, reflections, dreams, or past memories from external sources. Responds to 'remember this', 'capture', 'save to memory', 'I learned', 'note this down', or any request to persist information across sessions.
This skill should be used when the agent needs a reminder of what the memory system can do, what commands are available, or how the memory system works. Responds to 'memory help', 'what memory commands exist', 'how does my memory work', 'what can I remember', or any confusion about the memory system's capabilities. Also invoked by memory-boot after first boot to teach the agent the system.
This skill should be used at end of session, when wrapping up work, or when the user says 'close session', 'end session', 'session summary', 'sign off'. Writes session summary, enforces inbox aging, evaluates pending promotions, and updates active context.
This skill should be used after the agent writes or materially edits a concept, PRD, plan, spec, design document, strategy document, or similar planning artifact, and whenever the user says invoke James, run James, James this, or James-review. It reviews whether the document is self-contained inside project-owned scope, persists recipes and review chains under ~/.limitless/james, fixes what can be fixed, then resumes James for re-review until pass. Not for code review, article editing, or writing the initial document.