limitless

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 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 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.

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 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.