limitless

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.

This skill should be used when the user wants to create publishable content such as articles, blog posts, social media kits, slide decks, newsletters, or podcast transcripts. Covers multi-platform content generation (Substack, LinkedIn, Medium) in multiple languages, voice calibration, and AI image generation. Responds to "article-pack", "content pack", "write me an article", "Substack post", "LinkedIn article", "turn my notes into a blog post", "create a newsletter", or any request to research a topic and produce publishable material from it.

This skill should be used when the user wants to create, improve, test, or evaluate a Claude Code skill — new skills, skill edits, trigger tuning, or verifying a skill actually changes agent behavior. Responds to "dojo", "new skill", "write a skill", "turn this into a skill", "test this skill", "skill evals", "why isn't my skill triggering", "improve this skill description", or any request to build or harden a SKILL.md.

Use when warm-memory summaries should be rebuilt after meaningful memory changes or when the user asks to refresh, rebuild, or update the boot summaries. Runs the explicit refresh command and explains what artifacts were rebuilt.

This skill should be used when the user wants to build, prototype, or reshape an app, tool, CLI, API, automation, or feature by starting from the interaction surface first. Responds to "let's build", "prototype this", "I have an idea for an app/tool", "show me what it would look like", "surface first", "SFD", "click dummy", "what would the UX be", "what would the workflow look like", or any request where the user describes what something should do without specifying architecture. Converges on a working prototype before deriving contracts and building inward.

This skill should be used when the agent needs to evaluate or promote memory records through the trust pipeline. Responds to 'promote', 'evaluate inbox', 'elevate trust', 'promote to global', or when inbox items have accumulated and need triage. Converts inbox items to threads/lessons, elevates trust levels, promotes project knowledge to global.

Use when the user wants to start or reshape an app, tool, CLI, API, automation, or feature from the interaction surface first, by converging on a prototype before deriving contracts and building inward.

This skill should be used when the user says 'autopsy', 'shelve', 'done with this', 'extract value', or wants to close out a dead or shelved project. Extracts fascinations, writes a composting report, and feeds insights back into /spark.

This skill should be used when the user says 'build', 'slice', 'implement', 'harden', 'verify', 'what to build first', or is ready to start building from frozen contracts. Proposes vertical slices, implements one at a time, reports release readiness.

This skill should be used when the user says 'contract', 'derive', 'extract contracts', 'freeze', 'invariants', 'nfr', or wants to lock down requirements from a converged prototype. Derives contracts, invariants, and NFR targets, freezes on approval.

This skill should be used when the user says 'decide', 'what should I do?', 'plan', 'milestones', 'next steps', or has made a push/pivot/shelve decision that needs a concrete plan. Creates milestones with natural re-evaluation points.

This skill should be used when the user says 'explore', 'directions', 'design space', 'sketch', 'contrast', 'compare', or wants to see fundamentally different design approaches. Proposes 3-4 divergent directions with inline sketches and contrast capability.

This skill should be used when the user says 'fascination', 'what am I into', 'patterns', 'show my interests', or wants to browse their fascination index. Displays themes, intensities, and cross-fascination connections in list or Mermaid map mode.

This skill should be used when the user says 'narrow', 'decide', 'pick one', 'lock direction', or is ready to commit to one design direction from /explore. Synthesizes reactions into a recommendation, locks on acceptance.

This skill should be used when the user says 'patterns', 'what do I keep building?', 'meta', 'trends', or wants cross-project insight into recurring themes and habits. Analyzes fascination index and project history to surface patterns, abandonment trends, and deepest fascinations.

This skill should be used when the user says 'pulse', 'momentum', 'am I stuck?', 'check in', 'how is my project doing', or wants a momentum assessment. Analyzes git history, detects novelty depletion, and proposes push/pivot/shelve with a specific recommendation.

This skill should be used when the user says 'what should I do next', 'where am I', 'pyro', 'status', asks about project state, or needs lifecycle navigation. Reads project state and recommends the next skill to invoke. Also handles 'pyro init', 'pyro status', and 'pyro list'.

This skill should be used when the user says 'reframe', 'bored', 'novelty', 'stuck', 'different angle on remaining work', or wants fresh energy on stale tasks. Injects novelty through creative domain lenses — each lens produces one concrete actionable move.

This skill should be used when the user says 'remix', 'different angle', 'creative lens', 'what if we approached this differently', or wants to reframe their current idea through domain lenses (game design, music, architecture, etc.). Produces concrete alternative proposals.

This skill should be used when the user says 'revive', 'old project', 'bring back', 'resurrect', or wants to evaluate an abandoned repo. Archaeological analysis with scored revival options (full revival, soul transplant, organ harvest, graceful burial).

This skill should be used when the user says 'scope', 'cut', 'too big', 'soul', 'minimum viable', or the project feels overwhelming. Soul-preserving scope cuts — finds the minimum version that satisfies the core curiosity.

This skill should be used when the user says 'ship', 'release', 'publish', 'ready?', 'what's left', or wants to know what remains before shipping. Gap analysis between current state and shippable.

This skill should be used when the user says 'I have a vague idea', 'something bugs me about...', 'spark', 'help me figure out what to build', or describes a feeling or annoyance without a clear project concept. Excavates concrete ideas from vague feelings using propose-react-iterate.

This skill should be used when the user says 'surface', 'prototype', 'build it', 'show me', or wants a working interactive prototype from their locked direction. Iterates on behavioral critique until convergence.

This skill should be used when the user wants to pressure-test a feature, flow, or product idea by generating emotionally concrete future failure artifacts such as support tickets, angry emails, user complaints, one-star reviews, or postmortem fragments. Responds to "what could go wrong", "stress test this", "write a pre-mortem", "show me how this fails", "what would the support tickets look like", "pressure test this flow", or any request to make abstract risk viscerally real before or during design.

This skill should be used when the user wants a first-time user simulation — a cold-start walkthrough from the perspective of someone with zero context, zero author knowledge, and zero sympathy for what the builders intended. Responds to "pretend you're a new user", "do a first-contact pass", "test the onboarding", "is this obvious to a newcomer", "what would a stranger see here", "ghost user this", or any request to check whether the product relies on inside knowledge.

This skill should be used when the user wants to define a project's identity, build a lorebook, articulate what a product believes and refuses to become, or capture the implicit rules a project lives by. Responds to "what is this project trying to be", "the product is drifting", "write down the project values", "give this project a spine", "build a lorebook", or any moment when naming, tone, scope, or product identity feel undefined or are starting to drift.

This skill should be used when the user wants to audit, clean up, or redesign the naming in a product, workflow, or system — treating names as structural design decisions, not editorial polish. Responds to "the naming is a mess", "we call the same thing three different names", "clean up the terminology", "what should we call this", "the API and UI use different words", or any situation where muddy, overlapping, or conflicting names are distorting the user's mental model.

This skill should be used when the user wants to understand why a product, interface, writing style, or codebase feels unusually good, or to extract the hidden governing rules behind a reference. Responds to "I like this but I can't explain why", "what makes this work", "extract the design principles", "distill the taste", "what rules is this obeying", or any request to learn from a reference without copying it.

This skill should be used when the user wants help subtracting — identifying what to cut, delete, or deprioritize so the core product can breathe again. Responds to "what should I cut", "this is too bloated", "what can I delete", "simplify this", "what's diluting the core", "what would this look like with less", or any moment when a product, feature set, or roadmap is crowded, overcommitted, or accumulating obligations faster than conviction.

This skill should be used when the user wants to check whether a product, prototype, or workflow feels emotionally coherent — whether it seems like one mind made it, or whether different parts pull in different tonal directions. Responds to "does this feel coherent", "check the vibe", "this feels off", "does the tone match", "it works but it doesn't feel right", "review the emotional consistency", or any situation where correctness and usability are fine but something about the feel is wrong.

This skill should be used when the user needs live research, source verification, fact-checking, current comparisons, or updates to an existing research note. Responds to "look this up", "what's the latest on X", "compare X vs Y", "is this actually true", "fact check this", "update my research notes", or any question requiring evidence-grounded answers with strong next-step branching for deeper investigation.

This skill should be used when the agent needs to perform web searches, look up current information online, or gather search results from the internet. Provides privacy-respecting web search through a self-hosted SearXNG instance with structured JSON output. Responds to "search the web for", "look this up online", "find recent articles about", "what does Google say about", "web search", or any task requiring live internet search results. No API keys or external accounts needed.