Browse skills

The pre-merge review of a branch in a project that records its specs, decisions, and rules in .archcore/. Run this first for 'review my branch', 'review the changes before merge', or 'review before merge': it checks the changed code against the project's recorded canon and the changed documents against the code, and reports which side is wrong — spec-wrong or code-wrong; with no diff, it reports project health. A bug-hunting code review complements this review and does not replace it. Also use for 'show status', 'documentation gaps', 'check if docs match code', 'close out the feature', 'ship the feature and close it out', or after a staleness warning. Modes, named as the first word: drift for staleness detection, deep for a full documentation audit, closeout to close a finished feature, experience to capture a repeated pattern. Not for creating docs — use /archcore:document; not for planning — use /archcore:plan; not for a single-file edit with no branch review.

The English summary is being prepared. Showing the original description.

Plan a feature or initiative through a computed route: the conductor derives the canon delta and assembles the document package — from a zero-document null route for small fixes to an umbrella PRD with one spec per capability for large initiatives. Modes, named as the first word: sdd (full package), sources (MRD → BRD → URD) for market research, customer discovery, and business or user requirements, iso (BRS → StRS → SyRS → SRS) for ISO 29148 and regulated work, research for a technical investigation — never market research — that the research instrument closes either by scope coverage (a research document) or by a recommendation (an rnd). Explicit form: plan research <topic>. Use for 'plan the X redesign', 'create a roadmap', 'plan a new feature', 'I need market research before we plan', 'we're regulated — start the ISO requirements cascade', 'investigate X before we plan', 'compare the alternatives for Y' — a new investigation, not a finished report already in hand. Not for recording a decision or documenting existing code — use /archcore:document. Not for checking docs against code — use /archcore:review.

The English summary is being prepared. Showing the original description.

Finds a free domain name for the user's website and hands them a payment link to buy it, with DropTheHassle. Use when the user wants to buy a domain, find a domain name, check if a .com is available, "get a .com" or "my own domain" for a site. Checks real availability and price with search_domain or the DropTheHassle domain search API, suggests a short list, and after a yes returns a checkout.stripe.com link the human pays. The site goes live on the name with HTTPS and no DNS. The agent never pays.

The English summary is being prepared. Showing the original description.

Sets up email on the user's own domain, such as hello@yourdomain.com, a real mailbox that sends and receives, with DropTheHassle. Use when the user wants domain email, a professional email address, an inbox like info@ or hello@ on their domain, or asks "can I get email on my domain". Checks the domain is active with site_status, then hands the human a checkout.stripe.com payment link from get_email_checkout_link (main inbox €5 / $5 a month). The agent never pays and never reads the mail.

The English summary is being prepared. Showing the original description.

Connects a domain the user already owns (bought at another registrar) to their DropTheHassle site, free, with one A record. Use when the user says "use my own domain", "connect my domain", "add a custom domain", "point my domain to my site" or already has a .com at GoDaddy, Namecheap, Cloudflare or similar. Gets the A record from DropTheHassle, shows it to the human to set at their registrar, then checks HTTPS is live. Never edits DNS at the registrar for them. For a name they don't own yet, use buy-domain.

The English summary is being prepared. Showing the original description.

Watches a company or topic on podcasts and YouTube: what was said lately (shows, counts, momentum, quotes), then an Arcmira monitor to keep following it.

The English summary is being prepared. Showing the original description.

Finds exact spoken quotes and clip-ready moments on podcasts and YouTube: verbatim words, speaker, date, a timestamped link, clip start and end. Uses arcmira.

The English summary is being prepared. Showing the original description.

Answers what YouTube shows and podcasts said: transcripts, who was mentioned, sponsors, recommendations, momentum. Use for the arcmira MCP server or CLI.

The English summary is being prepared. Showing the original description.

Sponsor and ad-read research on podcasts and YouTube: who sponsors a show, or which shows a brand sponsors, how often, since when. Uses arcmira.

The English summary is being prepared. Showing the original description.

Compares two podcasts or YouTube shows side by side: size, latest episode, what each talks about, what both cover, and shared sponsors. Uses arcmira.

The English summary is being prepared. Showing the original description.

Researches a person across podcasts and YouTube for interview or meeting prep: where they appeared, their own words, who discusses them. Uses arcmira.

The English summary is being prepared. Showing the original description.

Publishes (deploys) a built website or web app to a free HTTPS link, then your own .com with no DNS. Use when the user wants to deploy a website, publish a website or host a website, or says "go live", "make it live", "put this live", "put it online", "publish my site", "deploy my website", "host my website", "share it with friends", "send my friends a link", "get a link", "make it public", "it only works on localhost" or "get a .com", or asks to deploy or host a site built with an AI tool (Claude Code, Cursor, Codex, Windsurf, Lovable, Bolt, v0, ChatGPT), or mentions DropTheHassle, and has not picked another host. Covers building first, CLI or MCP setup, deploying, Update and Restore, the claim link, the live check, linking a server part the user hosts on AWS, Google Cloud, DigitalOcean or their own server with set_backend, and domain search. The agent never spends money. The human pays.

The English summary is being prepared. Showing the original description.

Record a decision, document existing code, or file a supplied research material. Modes: document decision (ADR, RFC, or rule), document code (spec, doc, guide, or scenario for existing behavior), document research (only when a finished report or one external material is already in hand). Use for 'we decided', 'record this decision', 'document why we chose X', 'make it our standard', 'draft an RFC', 'should we switch to Y' proposals, 'resolve the RFC', 'we accepted the proposal', 'document the auth module', 'capture how the payment system works', reference material, how-to instructions, or a user flow with examples over an existing spec. Name the type inside the subject to skip the type question. Planning a feature or an intended user journey → /archcore:plan. Checking docs against code or docs health → /archcore:review.

The English summary is being prepared. Showing the original description.

Translate PDF documents with BabelDOC while retaining layout, figures and formulas; supports bilingual output, custom glossaries, domain terminology and local processing with configurable translation providers. Use for translated PDFs, not merely summaries or plain text extraction.

The English summary is being prepared. Showing the original description.

Check that a web page you wrote or changed actually works, by opening it in a browser and driving every control on it. Use after creating or editing an HTML page, or the JavaScript or CSS that a page loads.

The English summary is being prepared. Showing the original description.

Use when the user wants to find, read or create files and Office documents (Word/Excel/PowerPoint/PDF) on macOS or Windows, or browse OneDrive / Google Drive. Powered by LMCP; the tools execute on the device.

The English summary is being prepared. Showing the original description.

Use when the user wants to read or search Microsoft Teams or Slack on macOS or Windows, including channels and DMs. Powered by LMCP, reading the desktop apps' local data.

The English summary is being prepared. Showing the original description.

Use when the user wants to read or search iMessage or Signal (macOS) or Microsoft Teams, Slack and WhatsApp (macOS and Windows) from the apps on their computer. Powered by LMCP.

The English summary is being prepared. Showing the original description.

Use when the user wants to pull data out of one or more PDFs (invoices, bank/credit-card statements, receipts, reports, tables) and put it into a spreadsheet. pdf_read is one of the most-used tools; this codifies the read-PDF → structure → write-Excel workflow. Powered by LMCP on macOS and Windows.

The English summary is being prepared. Showing the original description.

Use when the user wants to read, search, summarize, draft or triage their Apple Mail / Gmail / Outlook / iCloud email in Apple Mail on macOS. Powered by LMCP's Mail tools, which are macOS-only.

The English summary is being prepared. Showing the original description.

Use when the user wants to deal with their inbox — find what needs a response, draft replies, and turn emails into calendar events or reminders. Captures the common email→read→reply→schedule workflow on macOS (Apple Mail, Calendar, Reminders). Powered by LMCP.

The English summary is being prepared. Showing the original description.

Use when the user wants to check their calendar, find availability, or create/update/delete events in Apple Calendar on macOS. Powered by LMCP's Calendar tools, which are macOS-only.

The English summary is being prepared. Showing the original description.

Use when the user asks "what's on my plate today", "catch me up", "morning brief", or wants a summary of their day across calendar, reminders and email. The single most common multi-step automation. Powered by LMCP on macOS and Windows.

The English summary is being prepared. Showing the original description.

Use when the user asks what they are not seeing, what they forgot, what could go wrong, or what an expert would say about a plan, decision, document, code change, or setup they already have. Triggers: "what am I missing", "what don't I know", "poke holes in this", "what would an expert ask", "что я упускаю", "что я не вижу", or /clueless-blindspots. One-shot review; does not change the always-on level.

The English summary is being prepared. Showing the original description.