Results for “build”

ScepticAgent packaging and Chrome Web Store publishing workflow. Use whenever the user wants to build the zip, package the extension, publish or submit to the Chrome Web Store, update the store listing, or deal with manifest/icon/permission requirements for publishing.

Repo housekeeping: sync READMEs to match current architecture, remove dead files (logs, screenshots, deprecated code, build artifacts), update npm/pip/cargo dependencies to latest. Use when asked to: "housekeep", "clean up repo", "update README", "update dependencies", "fix vulnerabilities", "remove dead code", "tidy.

Keep long-running agent work within 5-hour and weekly usage limits by checking usage between waves, pausing near the cap, and resuming only when the window is clear.

Builds a configurable scraping agent that collects data from APIs, HTML, or RSS, enriches it with Gemini AI scoring, and stores results in Notion, Google Sheets, Supabase, or local files.

Build a scalable outbound B2B sales machine with specialized SDR, AE, and CSM roles, using Cold Calling 2.0, referral emails, ANUM qualification, and pipeline math to generate predictable revenue.

Build and maintain a custom project skill repertoire. Always use at new project bootstrap and when users ask for new domain capabilities. Detect active assistant folders first, recommend at least 5 skills per search batch, confirm installs, normalize install paths, and regenerate workflow files.

Builds detailed voice profiles for characters, narrators, brands, or AI agents, covering diction, syntax, rhythm, worldview, signature patterns, and failure modes, and can reverse-engineer profiles from writing samples or audit existing ones.

Builds a multi-channel DSAR intake system supporting web form, email, phone, and in-person requests with identity verification tiers, automated routing logic, SLA tracking, and response generation. Activate for DSAR intake, rights request portal, multi-channel intake, SLA tracking, request management queries.

OI-3 spike harness — heavy consumer skill, FORKED arm. Builds an incident post-mortem and sources the readability standard mid-workflow via a forked (context fork) guidance skill. Use only when explicitly invoked by the spike harness with a TRIAL_ID and data path.

OI-3 spike harness — heavy consumer skill, INLINE arm. Builds an incident post-mortem and sources the readability standard mid-workflow via an inline (non-forked) guidance skill. Use only when explicitly invoked by the spike harness with a TRIAL_ID and data path.

Builds an interactive in-browser studio for tuning visual parameters (sliders, pickers, drag handles) or editing/annotating text and media, enabling real-time human-in-the-loop refinement instead of static comparisons or chat-based feedback.

Build, validate, and troubleshoot deep links for Codex, Cursor, VS Code, Visual Studio, and similar tools. Use when users ask for clickable links (especially in Slack) that open threads, files, folders, or app settings.

Classifies a repository into one of six archetypes and installs a curated bundle of agent skills covering build, test, review, deploy, and docs, with a user-visible manifest and a recorded stack file.

Use when planning a UIST cycle end to end — the late-March abstract and paper deadlines, the ten-week build-freeze before video production, the rebuttal window, conditional acceptance, the July camera-ready, adjunct-track parallel lanes, and the November conference — with owners and risk buffers.

Knowledge-base steward in the spirit of Niklas Luhmann's Zettelkasten. Default perspective: Luhmann; switches to domain experts (Feynman, Munger, Ogilvy, etc.) by task. Enforces atomic notes, connectivity, and validation loops. Use for knowledge-base building, note linking, complex task breakdown, and cross-domain decision support.

Create, inspect, and edit StateTree assets — states, tasks, transitions, conditions, considerations, and property bindings for AI behavior and game logic (StateTreeService). Use when the user asks to build a StateTree, add states/tasks/transitions, bind task properties, set up Utility AI considerations, or wire StateTree delegate transitions.

OI-3 spike harness — heavy consumer skill, BASELINE arm. Builds an incident post-mortem and sources the readability standard mid-workflow by reading a file directly, with NO Skill-tool call. Use only when explicitly invoked by the spike harness with a TRIAL_ID and data path.

Sets up a codebase for reliable agent-driven development by making it legible (structured docs, custom lints, code graph), executable (one-command dev stack, cloud sandbox), and verifiable (e2e gate, verify-before-ship loop).

Use to compute and monitor regulated complaint deadlines — acknowledgement, holding response, final response — against business-day calendars, and to find cases about to breach. Trigger for "are we meeting our complaint deadlines", "complaint SLA breaches", "final response deadline", "which complaints are about to breach", complaint ageing reports, or building a complaints deadline monitor.

Nx build system and monorepo tools. Advanced task orchestration, generators, and plugins. Use for complex enterprise monorepos with multiple technologies. USE WHEN: user mentions "Nx", "nx.json", "Nx monorepo", "Nx generators", asks about "Nx workspace", "affected commands", "module boundaries" DO NOT USE FOR: Turborepo (use turborepo skill), simple monorepos (Turborepo is simpler), single-package projects

Use when a task is well-defined, has an automatic way to verify success (tests, linter, build), and is tedious or large enough to benefit from unattended iteration - e.g. "get all tests passing", "implement this spec end to end", "fix every lint error". Not for one-shot changes or work that needs human judgment mid-stream.

Proposal pricing workflow producing defensible line-item, tiered, or value-based pricing with calibration and sanity checks. Use when the user needs a quote, estimate, tier packages, pricing strategy, rate calibration, or discount modeling for a proposal brief. Triggers: 'price this proposal', 'build tiered pricing', 'line-item estimate', 'value-based price', 'calibrate rates', 'sanity check this quote'.

Turborepo monorepo build system guidance. Triggers on: turbo.json, task pipelines, dependsOn, caching, remote cache, the "turbo" CLI, --filter, --affected, CI optimization, environment variables, internal packages, monorepo structure/best practices, and boundaries. Use when user: configures tasks/workflows/pipelines, creates packages, sets up monorepo, shares code between apps, runs changed/affected packages, debugs cache, or has apps/packages directories.

Prepare the demo video for a freelance bid — captures a clean screenshot of the gig's published n8n workflow via Claude in Chrome, builds a shot-by-shot recording script pairing the VSL narration with on-screen actions, and hands the founder tool-agnostic recording instructions (Loom/Tella/any recorder). The Demo phase of the Inbound Gig Engine. The founder records the video themselves.

Author or edit a custom HyperFrames composition when no specialized workflow fits, or when BRIEF.md sets flow: companion. Use for longer or multi-scene pieces, brand and sizzle reels, montages, static loops, static title cards, footage remixes, and freeform builds. Use motion-graphics instead for a short unnarrated motion-first unit, including an animated title. Route fresh creation through hyperframes before using this skill.

Deep Confidence Harness — a thinking, planning, and execution framework that forces structured reasoning before acting. Combines Monte Carlo scenario analysis, calibrated confidence, multi-perspective debate, and optimal path planning. Use before any complex decision, build, or task. Activates on: 'deep confidence', 'think before you act', 'plan first', 'Atlas mode', 'reason through this', 'what should I do', 'think this through', 'best approach', 'reason carefully', 'plan and execute'.

Use before any complex or ambiguous task where the path forward is unclear. For breaking down multi-step problems, choosing between approaches, clarifying vague requirements, identifying hidden assumptions, planning before building, and preventing costly mistakes from starting in the wrong direction. Activate when user says "how should I approach this", "what's the best way to", "I'm not sure how to", or presents a problem without a clear solution.

Verify an artifact that is about to leave the building — a partnership brief, pitch page, press release, customer email, RFP response, or any document sent to someone outside the org. Runs six checks before send — premise, confidentiality forward-test, evidence class, cold read by recipient personas, AI read, and tone metrics — and returns what to change with replacement copy. Use before sending anything outward-facing that carries customer detail, factual claims about a counterparty, or an ask.

Breaks natural-language problem descriptions into sub-tasks suitable for DAG nodes. The entry point of the meta-DAG. Identifies phases, dependencies, parallelization opportunities, and vague/pluripotent nodes that can't yet be specified. Uses domain meta-skills when available. Activate on "decompose task", "break down problem", "plan workflow", "what are the steps", "sub-tasks", "task breakdown". NOT for executing the decomposed tasks (use dag-runtime), building the DAG structure (use dag-planner), or matching skills to nodes (use dag-skills-matcher).

Turn a workflow that lives in your head into a runbook anyone can execute. Capture the 5W2H of a repeated process, who, what, when, where, why, how, and how much, name the failure points, and add the checks that prove each step worked, so the task no longer depends on you being available. Trigger on "write a runbook for this", "document this process", "make this an SOP", "turn this into steps", "how do we run X", or any workflow you have now done enough times to hand off.