No-Code Agentist

GROK BOT HOW TO USE WHAT NEW TODAY - Folder now 776 posts (14 new since Aug 30) - Official Elon: how to share your Grok Bot design with others https://t.co/l8LLJG1kAk - Official Elon: Grok Bot buys a Tesla https://t.co/VVxgzgq5tX - Official bot: get started here https://t.co/QL2bGF5hlF - Testers (blankspeaker): Plugins, add X, authenticate, and you get $100 in X API credits good for a year (new and existing devs) https://t.co/dYJffTxyLY - Testers (GrokInsider): if X API credits did not land, do not add the plugin yourself; ask Grok Bot to connect X so an Authorize card opens the browser https://t.co/BYIFWxLKLa - Testers (XFreeze): do not create a Bot yourself; ask a Bot to create a capable Bot for you (it already has your context, tools, and workflows) https://t.co/Rvi1vzmbcA - Testers (farzyness): a Bot can exclusively use Grok Build in CLI with the latest Grok models at highest thinking (copyable "Researchy") https://t.co/1jGc1hizka - Testers (Damir_Akaza): 4 Bots in a group chat built and launched a Meta ads campaign in 40 minutes (local Mac Mini via Tailscale, 50 creatives, 9 ads live); tester says Grok still trails Claude Code and can hallucinate copy https://t.co/IrQvPlCTWJ - Testers (Michael_Fenech_): give it business responsibilities, not questions; start with checking, chasing, updating, coordinating (recruitment, e-comm, real estate, accounting, legal, SaaS, agencies, trades, founder ops) https://t.co/ID3hmNI4H1 - Testers (GrokBotDev): five role templates, Jess (email/calendar/Notion/Slack recap), Marketing Bot, Prospecting Sheet Builder, Reaper (kill unused subs/meetings), Human Copywriter https://t.co/y2SNdsVDlv - Testers (nateherk): recorded a 2-hour Grok Bot course, linked in replies https://t.co/4xENzQnYWe - Testers (BrianRoemmele): GrokPod 1.0, a 40mm device for Grok and Grok Bot over cellular or WiFi; listen mode for hours; still in testing, plans to open source https://t.co/rBT6fb8aIC - Testers (francescoinweb3): claims building finance, trading, airport, and restaurant products, now a "Grok City" holding view that keeps running when the terminal is closed https://t.co/bTSbZiRMqg https://t.co/jHsuO4JFaG WHAT IT IS - A Bot is a named, persistent teammate, not a one-off chat - You message it like a coworker and it finishes work in real apps - All of your Bots share one cloud computer (browser, files, terminal) - Each Bot has its own screen on that shared computer - Work keeps going when your laptop or the app is closed - It only comes back when it needs approval or a human step - Do not confuse Grok Bot with Digital Optimus (real-time video human emulation) - Testers (joehansen): do not confuse Grok Bot with an X Chat Agent (an X account you add to a group chat). Grok Bot is the machine that does the work ACCESS AND INSTALL - Official bot (Aug 26): All SuperGrok and Cursor Pro subscribers now have access - Testers quoting SpaceXAI (cb_doge): SuperGrok, SuperGrok Plus, SuperGrok Heavy, Cursor Pro, Cursor Pro+, Cursor Ultra, Cursor Teams Standard and Premium - Cursor CEO Michael Truell: everyone with a standard Grok or Cursor subscription - Testers: included at no extra cost with those plans; circulating plan prices $20/month Cursor Pro and $25/month SuperGrok (nextbigfuture) - Official bot + Elon: weekly / free usage limits reset for all Grok Bot users - Sign in with your Cursor account (that account owns plan and usage) - Official desktop download: https://t.co/tHvaZ7icnr - Also listed at https://t.co/bfJPYFHLZz - Official desktop is macOS and Windows (Apple silicon or Intel; Windows x64 or Arm64) - Official docs say Linux desktop is not currently available - iPhone: iOS 18+, App Store app "Grok Bot" - Official docs still say iPad and Android are not supported yet for actual use - Grok Bot team (poteto, Aug 27): Android app almost ready; pre-register on Google Play https://t.co/o7XKDJuWcv - Testers quoting SpaceXAI (cb_doge): Android app available for pre-registration on Google Play - SuperGrok Heavy users can choose Get access with SuperGrok Heavy, then Link Grok Account - Linking SuperGrok Heavy can unlock free Cursor Ultra (one Grok account to one Cursor account) - Legacy Privacy Mode blocks Grok Bot; switch to a supported Cursor data setting first - Grok Bot checks for updates automatically; Check for Updates is in Settings → Beta - Bookmark testers: iPad may be coming soon; official docs still say iPad is not supported yet SIGN IN - Desktop: Get started, then Sign In with Cursor in the browser - iOS: Login with Cursor, finish in the browser, return to the app - Official: Cmd-D turns on voice dictation - Official: it is easier to use the remote computer from your phone - Use the same Cursor account that should own usage - First-run tour asks which tools you use; that only shapes teammate suggestions - Computer setup runs in the background, then Meet a future teammate opens CREATE A BOT - New in the sidebar, or Cmd/Ctrl+N - In New chat, choose Create new agent - Edit Profile: name, title, description, avatar - Give a short name, one primary job, and how it should work - Description = standing rules (never send without approval) - Chat messages = this-task instructions (draft follow-ups for these 12 accounts) - Focused Bots beat one catch-all General Helper - Testers (XFreeze): do not design a Bot from scratch; ask a Bot to create a capable one for you (it already has your context) - Bookmark testers: start with about six roles; give each Bot recurring work - Pin important Bots; hide unused ones (hiding does not pause routines) - Bookmark testers: resize the sidebar, give titles, and group Bots into sections - Duplicate a Bot to reuse a role for a new scope (copy does not include memory or history) - Delete only if you are sure; files and logins on the shared computer stay - Account limit: 50 Bots and group chats combined - Name language can steer reply language (bookmark testers reported this) - Bookmark testers: no model picker yet; testers still list voice mode, BYOK, multiplayer, hang-error messages, and a real iPad app as missing HOW TO WRITE A TASK - Outcome: what should be finished - Sources: which apps, sites, files, or chats matter - Constraints: what it must not do, or must ask first - Deliverable: what it should return - Review point: when it should stop for you - Safe first task: attach a file and ask for a cited summary; do not change the file - Next task: one real tool, read-only, with a sign-in handoff if needed - After a good result, name the lasting format preference in chat - Then save it as a skill or routine - Official bot examples: email cleanup, Starlink-likely flights, build a site then buy the domain and deploy, meeting notes, sales prospecting, refunds, podcast audio digest - Testers: paste a viral video link and ask the Bot to recreate it - Testers: start from an org chart or make one Bot the boss of a repo, not a long to-do list - Testers: one clear job, explicit allowed sources, no-guessing rule, approval gate before any real action - Testers: 5 calibrations — confidence threshold, checkpoint long tasks, show negative examples, gate destructive actions separately, test edge cases first - Testers: one Bot, one job — two jobs claimed worse at both; put recurring work on a schedule - Testers quoting claimed SpaceXAI employee: version prompts and tool configs like code; scratchpad separate from the user-facing answer; retry with a different strategy; measure cost per successful outcome; review failure logs on a schedule - Testers (mvanhorn): Compound Engineering — force a plan first; three-layer instructions (base, role, current focus); screenshot instead of retyping what's on screen; ping only on a real hit - Testers (AlexFinn): anything you are about to do on your computer, ask Grok Bot first - Testers (AlexFinn): example week — Reddit microSaaS, 3D digital office to watch Bots, Omarchy setup, product returns, daily AI news post, Cursor cloud-agent bug fixes, X model-release watch, brand-deal negotiation, contract redlines - Testers (Michael_Fenech_): give it business responsibilities (checking, chasing, updating, coordinating), not just questions AGENT COMPUTER AND LOGINS - Open Agent Computer from the conversation to watch the desktop - Take over for password, passkey, 2FA, CAPTCHA, payment, or human-only pages - Complete only the blocked step, then return control - Never paste passwords or one-time codes into chat - Use a secure secret request when the app offers one - Browser sessions persist and are shared across all your Bots - Prefer a connector/plugin when one exists; use the browser when it does not - Keep durable files in /workspace with clear project folders - Settings → Beta: Update Agent Computer (preserve state), Recover, or Reset (can lose recent work) - The cloud computer is not your Mac or Windows machine - Local-computer execution is separate: Settings → General → Agent → Execution on Local Computer - Default local policy is Ask every time; use Never allowed unless you need local files - Bookmark testers: give a Bot full local Mac/iMessage access only on a spare machine - Testers: local Mac access can write local Python scripts on your Mac - Testers (Av1dlive / mvanhorn): Claude Code, Codex, and Cursor claimed runnable on the Bot's own computer - Testers (XFreeze): take over that same cloud computer from your phone without being at the laptop - Testers (Damir_Akaza): group-chat Bots can reach a local Mac Mini via Tailscale for project files and local scripts - Testers (farzyness): a Bot can exclusively use Grok Build in CLI with the latest Grok models at highest thinking - Testers (AlexFinn): a 3D digital office on a second monitor to watch Bots work PLUGINS AND CONNECTORS - Settings → Plugins, then Add, then authenticate in the browser - Type @ to attach a connector; type / to reference a saved skill - Installed connectors are account-wide, not isolated to one Bot - Official: you can connect multiple accounts to the same plugin - Official bot (Aug 26): SuperGrok and Cursor Pro now included; weekly limits reset. Testers quoting SpaceXAI: also Plus/Heavy/Pro+/Ultra/Teams - Testers: give a Bot its own email address so it can send and receive on its own - Testers (mvanhorn): give a Bot its own inbox, not your Gmail (one mistake should not flag your domain); Twilio number so a Bot can make calls - Testers: app v0.23.0 adds creating new channels - Official bot: improved X support — connect your X profile; a developer account is auto-created with included credits https://t.co/NBucim48w4 - Testers (blankspeaker): Plugins, add X, authenticate; $100 in X API credits good for a year (new and existing devs) - Testers (GrokInsider): if credits did not land, ask Grok Bot to connect X so the Authorize card opens the browser; tester's manual plugin add failed - Follow the Connect card when a Bot asks for a plugin - Bookmark testers: X connector may still need a paid X API key in some setups (official path now auto-creates a developer account with credits) - Bookmark testers: image generation works; testers now also claim video editing (music sync). Video generation still unconfirmed. Testers (XFreeze): dedicated video-editor Bot for footage → clips/cuts/sound/titles - Bookmark testers: Grok Bot can now read your X bookmarks - Testers (testerlabor): you can link your X Premium+ subscription to Grok Bot - Testers: Higgsfield x Grok Bot; 100 free credits for new users - Testers: send a YouTube link with start/end timestamps and get an HD clip in chat (Google login claimed) - Testers: give a Bot Grok Build + Cursor CLI so weekly limits can be spread across Cursor and Grok SKILLS AND ROUTINES - Skill = reusable how-to (steps, rules, output, approval boundary) - Routine = when to run that work (schedule or event) - Do the task once, make it reliable, save a skill, then automate - Teach a task: open computer view, choose Teach a task, demo up to 10 minutes, review the draft skill - Teaching records the screen, not microphone audio; do not expose secrets while teaching - If Teach a task is missing, ask the Bot to write a skill from the completed work - Create a routine on the Bot that should own the job - Confirm owner, schedule, time zone, input, result, approval, and missing-data behavior - Event triggers (Slack, GitHub) are separate from plugins and need their own connection - Keep event matchers narrow; avoid every new message - Test run does real work; use safe inputs - Testers quoting docs: Test can send real emails to real clients; Stop is a brake, not a rewind - View conversation details → Routines to pause, edit, inspect, or delete - A Bot can own 50 routines; last 20 run records are kept - Deleting a routine has no undo - Testers quoting docs: delete a Bot and every routine on it dies; no undo - Long absence can pause unattended routines until you confirm - Bookmark testers: Teach a task from + in the browser, record yourself, then let the Bot replay it - Testers: skills taught to one bot claimed available across the account team on the same computer - Official Elon: how to share your Grok Bot design with others https://t.co/l8LLJG1kAk - Testers: a reusable-skills source claimed (BrianRoemmele) - Testers quoting Grok Bot team (0xMorlex): keep recurring routines off the main agent's context - Testers (mvanhorn): Teach by recording and respect the 10-minute cap MULTI BOT TEAMS - Start with one Bot that owns an end-to-end outcome - Add a specialist only when the role is stable - Use a group chat when the handoff itself should be visible - Bots can message each other and pass ownership - Do not treat separate Bots as a security boundary (they share the computer) - Keep sending, buying, deleting, publishing, and production changes behind approval - Bookmark testers: a Bot may create other Bots before it can delete them - Bookmark testers: tell a hub Bot to loop a specialist every few minutes and watch it - Testers: put Bots in one group chat, appoint a Chief of Staff, and stop being the router - Testers: isolate each Bot's job and add a supervisor; a crew without that can perform worse - Testers: night-shift crews (chief, scout, forge, critic, ship, ledger) share one computer; human gate for merge, production, spend, send, delete - Testers: one group chat per job/post, not per Bot; you only message the Chief of Staff - Testers: show the workflow once on screen rather than writing a long spec - Testers: add a RED TEAM Bot whose job is to disprove the thesis; no single source closes a claim - Testers quoting Grok Bot team (0xMorlex): specialist roles (designer/engineer/PM); organize projects without a new Bot for everything; a Chief of Agents that creates and manages the rest - Testers (mvanhorn): Bot Advisor whose only job is building and tightening other Bots; files are the memory bus between Bots - Testers (Damir_Akaza): 4 Bots in one group chat split a Meta ads campaign (creatives, fact-check, deploy) with autonomous handoff IOS - Same Bots, chats, routines, plugins, and cloud computer as desktop - Send text, dictate, attach photos/files, mention Bots, reply in threads - Take over the computer for login/2FA from the phone - You can pause or resume a routine on iOS - Editing schedule, run history, test, delete, and teach-by-demo still need desktop - Enable notifications for results, questions, and approvals - Testers: phone notification shows the proposed action; approve or deny - Testers (XFreeze): you can operate and take over the Bot's computer from your phone as long as it has internet - Grok Bot team (poteto): Android app in Google Play pre-registration, not shipping yet. Official docs still say Android is not supported APPROVALS AND SAFETY - Put the stop line in the request: draft, do not send; ask after showing current vs proposed - Desktop: Allow once, Deny, or Always allow a matching rule - iPhone: Approve once or Deny - Auto Review: Settings → General → Auto-review - Require Approval beats Always Allow when both match - Write narrow rules, not allow everything in the browser - Do not approve an action you cannot identify - Connect only the tools the workflow needs - Start read-only; keep spend, send, publish, delete, and production behind approval - Sign out and revoke connectors when access should end - Deleting a Bot does not wipe shared files or browser sessions - Bookmark testers: delay standing inbox/CRM access until you trust the beta - Bookmark testers: one person burned a 7-day quota in about 8 hours - Bookmark testers: SuperGrok may offer one-off usage resets in settings; use before they expire - Testers: gate destructive actions (delete, overwrite, irreversible send) as their own confirmation, not lumped with routine tool use - Testers quoting docs: Test run does real work; Stop does not unsend - Testers quoting Elon (cb_doge): connecting a Bot to a bank account; Elon said any loss from a bot mistake would be covered. Still keep spend behind approval - Official bot Link shopping: keep purchases behind approval even though the Bot can complete them on your behalf - Official Elon: Grok Bot buys a Tesla https://t.co/VVxgzgq5tX - Testers (mvanhorn): unsupervised crews claimed to multiply their own errors ~17x; draft-then-approve anything that sends; most Bots that don't own an outcome fail - Testers (antpalkin): end every agent's job with a hard never-without-asking list; give one Bot veto/kill power whose no beats the rest of the desk FIRST BOTS WORTH CREATING - Inbox manager for email and Slack triage - Calendar and reservation Bot - Research and daily brief Bot - Coding Bot that can launch Cursor cloud agents - Chief-of-staff hub that routes work to specialists - Personal errands Bot (tickets, food, travel, forms) - Content Bot that drafts in your voice for approval - Chief-of-staff that researches you, organizes the other Bots, and can turn the digest into a morning podcast - Testers (mvanhorn): Bot Advisor; own-inbox Bot; a call Bot with its own number - Testers (techdevnotes): default Bots circulating — Night Shift (overnight digest), Inbox Triage, Chief of Staff, Negotiator, Prototyper, Researcher, Shopper, Apartment Scout, Lookout, Competitor Watcher - Testers (techdevnotes): also tool-specific sales/ops/dev roles (CRM scribe, pipeline scout, ticket triager, QA, dashboard watcher) - Official bot + Link: Shopper Bot can now complete online purchases once link is connected (keep approval on) - Testers / SpaceXAI (kiaraplds): flights, tickets, groceries — delegate errands safely to your Bot - Testers (minchoi): one-person-company setups — money, appointments, running ops from the phone - Testers (niccruzpatane): Accounting Bot (invoices, spending, bills); Personal Bot (flights, rides, Airbnb, Google Calendar, Amazon orders/returns); Home Bot (lights, robots, speakers, thermostats) - Testers (GrokBotDev): Jess (email/calendar/Notion/Slack recap), Marketing Bot, Prospecting Sheet Builder, Reaper (kill unused subs/meetings), Human Copywriter - Testers (Michael_Fenech_): start in recruitment, e-comm, real estate, accounting, legal, SaaS, agencies, trades, founder ops OFFICIAL LINKS - Overview: https://t.co/9mNf9wYB2Z - Get started: https://t.co/rQcegaIoXt - Create Bots: https://t.co/PSwBI5rKOF - Skills and routines: https://t.co/mWpdmvfrJe - Computer and apps: https://t.co/9cF9X2yclW - Approvals and privacy: https://t.co/7vJXP85Xjd - iOS: https://t.co/s8KDfkyMTy - Cursor getting started: https://t.co/7mTr5JItza - SuperGrok Heavy link: https://t.co/suly1Xv6DP - Launch post: https://t.co/SHbPpOL9if - Download: https://t.co/tHvaZ7icnr

Everything Grok bot. full breakdown https://t.co/ZtrH2Vm5nY

Grok Bot gets messy fast when every Bot tries to do everything What held for me: - Bot architects - Cursor Cloud Agents do repo work - 1 control block + 1 job per Bot Less overlap. Cleaner memory. Lower Bot usage. 3 copy-paste blocks inside https://x.com/i/article/2094340806991597568

everyone is looking at grok bot like it is five new employees the more interesting part is that they are not five isolated employees they share one persistent cloud environment: the same browser sessions, terminal, filesystem and authenticated tools - while a chief of staff can route work between them without waiting for you to open the laptop that turns one login into infrastructure a research bot can collect leads, pass them to a writer, hand the result to a designer and let an ops bot update the workflow all inside the same running machine the upside is obvious: less copying, fewer handoffs and work that continues while you sleep the blast radius is just as obvious: - authenticate only the services the whole agent fleet is allowed to reach - give every bot a narrow role description, because that description becomes its place in the org chart - keep irreversible actions behind human approval: sending, publishing, spending and production changes - store skills, configuration and long-term state inside `/workspace`, because the rest of the VM may disappear during an update - treat shared sessions as shared authority, not as separate bot identities the same architecture that makes grok bot useful is what makes it dangerous to configure casually my take: the breakthrough is not that you can hire five AI workers it is that they can operate like one persistent company inside your real tools and your job changes from prompting every task to designing the permissions, boundaries and handoffs the full chief-of-staff setup, session handoff model, approval matrix and `/workspace` survival strategy are mapped out in the article ↓

No office. No payroll. No Slack. 8 AI agents run research, content, outreach, and finance while I sleep. Here's the exact setup — role by role, mistake by mistake. https://x.com/i/article/2094147144382922752

Before you pay an "org brain" vendor, read this. https://t.co/E0hXph5NVX

LLM Integration & Bring Your Own Key on NeoTrade @NeoSoulAI @Hansmahanakon NeoTrade is an AI trading agent that runs on your machine. The agent needs an LLM to research markets, estimate probabilities, and form a judgment. This piece covers how you connect a model, why live trading requires one, and how to use your own key. The agent will not run without an LLM credential. If none is bound, the app says “no model.” Connecting a model takes two steps. If you use your own key, open Settings, then LLM, and paste the API key. Then open the agent, go to Config, then Model, and assign that credential. Signing in with a NeoTrade account also gives you a house credential. You still have to assign a model in the agent’s Config. Having a key somewhere in Settings is not enough. Keys are write only. The app will tell you whether a key is stored. It will not show the key again. The key does not appear in logs or RPC requests. Paper trading is the place to try the loop first. When you switch to real money on predict or Polymarket, the go live checklist asks for more. The wallet must be unlocked and funded on the venue’s chain. The venue account must be ready. Risk limits must be set. An LLM must be connected, because live trading uses adversarial review. Adversarial review is a second pass. Another model challenges the agent’s thesis: missing evidence, weak assumptions, contradictions. You see the original case and the counter case before you approve an order. That layer does not replace limits. Limits live in code, in the decision gate. The agent cannot talk its way into a higher cap. Review only stresses the reasoning. The order still has to clear edge, bankroll fraction, and position limits. You can power the model in two ways. Sign in with a NeoTrade account and use the house credential; inference is billed through the platform. Or bring your own key in Settings, then LLM; inference is billed by your provider. BYOK means requests run with your OpenAI, Anthropic, or other provider key. You keep the bill, the rate limits, and the data terms with that provider. A few practical notes. No key and no model assignment means “no model.” Wallet keys and LLM keys stay on your machine. NeoTrade does not custody funds and does not display secrets. Web pages and API responses enter the agent as untrusted data, not as instructions, which cuts down prompt injection. Start on Paper, then go live. Use Settings, then LLM, if you want your own key. Assign the model in each agent’s Config. Before real money, the checklist must show an LLM connected, or adversarial review cannot run. Keep the first live agent in Copilot. Read the judgment and the opposing view. Widen limits or turn on Auto only after that. NeoTrade separates intelligence from signing authority. You pick the model and the key. The wallet and the coded limits still govern capital. On live, the model has to be good enough to survive adversarial review, not just good enough to chat.

Andrej Karpathy has access to some of the best AI systems in the world. But the interesting part isn't which AI he uses. It's what he actually does with it. I went through his AI workflows and found 7 habits that completely change how you work with these tools: 1. He doesn't obsess over prompts. Instead of spending 5 minutes typing the “perfect” prompt, he uses speech-to-text and dumps his thoughts into the AI. Messy thoughts. Half-formed ideas. Long explanations. Everything. Because speaking is roughly 3x faster than typing, he can give the model far more context without wasting time polishing the prompt. And modern models are good enough to structure that mess themselves. 2. He builds an “LLM Wiki.” Instead of expecting the model to magically know everything about a project, he gives it the actual material: → PDFs → reports → documents → research → project data The AI then works from that material instead of giving you a generic answer based on its memory. This is especially useful for large projects where the quality of the answer depends heavily on the context. 3. He interrogates documents instead of just reading them. This is one of the best research workflows in the script. Load a paper, report, or collection of sources into something like NotebookLM. Then don't just ask for a summary. Question it. Challenge the claims. Ask follow-ups. Make it explain confusing sections. Use mind maps and flashcards to explore the material. You're no longer passively consuming a document. You're actively interrogating it. 4. He goes to the data instead of stopping at opinions. When he wanted to understand which jobs are exposed to AI, he didn't rely purely on headlines and commentary. He had AI pull actual employment data from the Bureau of Labor Statistics and turn it into a spreadsheet. That's a completely different research loop: Question → raw data → spreadsheet → analysis → charts Instead of asking AI what everyone thinks is happening, get the underlying numbers and investigate them yourself. 5. He gives AI persistent context. Nobody likes opening a new chat and explaining the same project from scratch. So Karpathy's LLM Wiki idea can become a persistent knowledge base. A folder of text files containing useful information about your work. And with something like claude.md, you can give Claude instructions it reads whenever you start working. Your AI doesn't have to begin every conversation from zero. 6. He gives AI bigger jobs. This is where most people dramatically underuse agents. Instead of: “write this function” give it: “build this feature.” Instead of: “give me some ideas” give it: “research this entire topic.” Karpathy has described moving from writing most of his code manually toward letting AI agents handle much larger chunks of the work. The goal isn't to automate one tiny action. It's to delegate an entire piece of the problem. 7. Then he runs multiple agents at once. This is probably the most interesting part. If one agent can handle a large task... why stop at one? You can have several chats running simultaneously, each with a different responsibility. One researches. One analyzes. One writes. One reviews. One improves. And for more advanced workflows, you can have one agent orchestrate multiple sub-agents. That's essentially an AI team working in parallel. So the biggest takeaway from Karpathy's workflow isn't some secret prompt. It's a change in how you assign work. Don't just ask AI for answers. Give it context, data, memory, ownership, and parallel work. The jump is from: “help me with this task” to: “take this entire piece of work and figure it out.”

Most people repeat the same explanation to Claude every single week and never notice they are doing it. Every repeated explanation is a skill you haven't built yet. A skill is a folder with one file in it. SKILL.md holds a name, a description, and your steps in plain English. The description is the part almost everyone gets wrong: it decides when the skill triggers, so write it like a rule, not a title. You don't even have to write it. Ask Claude to interview you about the task, then draft the skill itself. Ten minutes, once. From then on it's a slash command. It works in every new chat, it auto-triggers when a matching task shows up, and when the output drifts you fix the skill once instead of fixing every prompt forever. Then stack: a project holds the work in front of you, skills hold the processes, a scheduled task runs them without you. One skill a week and by December you've built a team. Bookmark this for the next task you catch yourself re-explaining.