Loading...
Loading...
Found 14 Skills
Working memory for thinking out loud.
Stand up (or extend) an operator-only in-app scratchpad / internal test-bed — a single gated internal page that reuses the project's real components and library functions so you can judge work-in-progress by eye: eyeball generated visuals (OG/social cards, emails, avatars, empty states), compare variants side by side or with live sliders, check config/env readiness, and exercise real side-effecting flows with fake data — without shipping any of it to users or clicking through the whole product. Boards and config panels get a "Copy as JSON" button so a tuned-by-eye result round-trips straight back into the code or to an agent to apply. Bootstraps into the user's existing stack: detects the framework, auth, and env conventions, writes a fail-closed access gate first, then a route with a section switcher seeded from their own code. Use when a user says "spin up a scratchpad", "internal test bed / dev playground / sandbox page", "an operator/admin preview page", "a page to eyeball my work", "preview my OG cards / emails / component variants", "add a test page for these components", or "an internal page to exercise a flow with fake data". NOT for public/user-facing features, NOT a replacement for tests (pass/fail machine-checkable → write a test), NOT Storybook (this lives inside the real app), and NOT a place to do load-bearing production operations.
Extract actionable Linear tickets from ambiguous input — Slack conversations, call transcripts, screenshots, meeting notes, or any unstructured material. Proposes tickets in a scratchpad file for user review, then creates them in Linear on approval. Use when the user wants to turn conversations, transcripts, screenshots, or notes into Linear tickets. Also use when user says "create tickets from this", "send to linear", "make issues from this call/chat", or provides raw material and asks for tickets.
Laserfocus platform help — Salesforce overlay with Stacks, table views, bulk editing, precache technology, and task management. Use when reps find native Salesforce UI too complex for daily pipeline work, Salesforce data entry is slow and reps skip updates, evaluating Laserfocus vs Scratchpad vs Weflow vs Dooly for Salesforce overlay, need a lightweight Salesforce alternative without replacing the CRM, or Laserfocus Stacks or Field Groups not working as expected. Do NOT use for general CRM selection (use /sales-crm-selection) or conversation intelligence / call recording (use /sales-note-taker).
How to explore and make sense of PostHog Signals scouts — the scheduled agents that scan a project and emit findings into the Signals inbox. Use when a user wants to understand what scouts they have, how each one is behaving, and whether the fleet is actually working. Covers surveying the fleet and its schedules, reading recent scout runs and drilling into a single run's reasoning, inspecting the durable scratchpad memory the fleet has built up, tracing a run to the findings it emitted, and assessing a scout's health and performance over time (cadence, success rate, emit rate, signal-to-noise). Read-only and exploratory — to write or tune a scout, use `authoring-signals-scouts` instead. Trigger on "what are my scouts doing", "how is my <x> scout performing", "show me recent scout runs", "why did this scout find/emit nothing", "what has the fleet learned", "explore scout run <id>", "is my scout working".
Veloxy platform help — Salesforce-native field sales enablement with predictive intelligence, geolocation route planning, email tracking, and mobile CRM. Use when configuring Veloxy for a field sales team, Veloxy emails stopped sending or email sync breaking, Veloxy geolocation not showing nearby leads, Veloxy mobile app crashing or lead status not updating, comparing Veloxy to Scratchpad or Weflow or Badger Maps for Salesforce field reps, Veloxy Lite drip campaigns not triggering, or evaluating field sales software for outside reps on Salesforce. Do NOT use for conversation intelligence or meeting recording (use /sales-note-taker) or general CRM selection (use /sales-crm-selection).
This skill should be used when agent work needs file-backed context: durable scratchpads, tool-output offloading, just-in-time discovery, cross-agent handoff files, filesystem memory, or cleanup policies for context stored outside the prompt.
Batch-process web pages via headless Playwright browser, extract HTML, convert to markdown using Turndown, and save to timestamped scratchpad file. Use when user asks to "capture these pages as markdown", "save web content", "fetch and convert webpages", or needs clean markdown from HTML. All URLs from one prompt → single file at docs/web-captures/<timestamp>.md.
Signals scout that watches a PostHog project's most-viewed dashboards and insights for recent anomalies — sudden bursts, drops, flat-lines, and trend breaks at the daily or hourly level. It discovers what the team actually looks at (view counts, dashboard access), curates a durable watchlist in the scratchpad, and balances re-checking known high-value insights (exploit) against discovering new ones (explore) across runs, since no single run can cover a busy project. Anomalies are scored by robust deviation from each insight's own seasonality-matched baseline; it emits a finding only when a move clears the confidence bar, otherwise it updates the baseline memory and closes out empty. Self-contained peer in the signals-scout-* fleet.
Execute approved implementation plans from scratchpad. Use when implementing a previously planned feature.
Project status dashboard — open issues, recent commits, active branches/worktrees, memory state, and scratchpad. Use when the user asks for a status report, project overview, "what's going on", "where are we", or wants to catch up on project state without the full /catchup reconstruction.
Multi-agent coordination, inter-terminal messaging bus, distributed file/mutex locking with monotonic fencing tokens, orchestrating multi-stage DAG task pipelines, cluster health watchdog sweeping, and worker queues over Redis. Use when coordinating work between multiple AI assistants or terminal sessions, acquiring distributed mutex locks before editing shared files or running migrations/deployments, generating monotonic fencing tokens to prevent zombie writes, dispatching tasks or RPC queries to peer agents, producing/consuming from competing-consumer work queues, orchestrating multi-stage pipelines with automatic dependency resolution, reliably claiming tasks with leases and ack/DLQ handling, scattering tasks to a pool for quorum aggregation, sharing scratchpad memory, managing floor control in roundtable brainstorming, setting and checking run cancellation tokens, running blind consensus ballots without anchoring bias, electing resilient mesh leaders with automated lease failover, auditing cluster health and sweeping dead agent/listener garbage, or discovering active teammates and their status. Triggers: 'coordinate with the other terminal/agent', 'talk to agent', 'send task to', 'ask the other assistant', 'inter-agent chat', 'lock file', 'lock resource', 'mutex lock', 'prevent concurrent edits', 'fencing token', 'monotonic counter', 'zombie writes', 'work queue', 'enqueue task', 'claim task', 'ack task', 'reliable queue', 'dead letter queue', 'dlq', 'blackboard', 'scratchpad', 'shared memory', 'floor control', 'speaker ring', 'moderated roundtable', 'pass floor', 'yield floor', 'cancel task', 'cancel run', 'cancellation token', 'abort run', 'ballot', 'vote', 'consensus', 'blind voting', 'leader election', 'acquire leader', 'failover', 'mesh leader', 'scatter', 'gather', 'quorum', 'workflow', 'dag', 'pipeline', 'task dependencies', 'resolve step', 'workflow next', 'sweep', 'clean dead agents', 'stale locks', 'garbage collection', 'cluster watchdog', 'who is online', 'agent status', 'locutus', 'Redis bus'.