Results for “one-shot”

13 skills
More results
rajanthar
webwright
Solve a user-specified web task code-as-action style by driving a local Playwright browser through one bash command at a time, saving screenshots and an action log into `final_runs/run_id/`, and visually verifying the result. Use when the user asks to automate a web task (search, filter, form-fill, multi-step flow, data extraction) and wants reusable scripts plus screenshot evidence rather than a one-shot answer.
0 · bundle
neuralblitz
camsnap
Capture snapshots, clips, or motion events from RTSP/ONVIF cameras using the camsnap CLI.
1
heath-gtm
trigger-outreach
Turn a buying signal into a timely, relevant touch. Read the trigger (funding, a new hire, a product launch, a job posting, a tech change), pick the angle it earns, and write the outreach while it is still fresh. Built for B2B outbound teams, customizable to your signals and your voice. Trigger on "someone just raised, what do I send", "they posted a job, draft outreach", "new VP started, reach out", "write a touch off this news", or any signal-to-message task.
0 · bundle
antigravity
handoff
Compact the current conversation into a handoff document for another agent to pick up, including suggested skills and references to existing artifacts.
42.4k
jiachen-t-wang
llava-onevision-easy-visual-task-transfer-arxiv-2408-03326v2
LLaVA-OneVision: Easy Visual Task Transfer
6
joshuashepherd
tam-headshot-source
Acquires a single verified headshot per named leader from official sources, with identity checks and a provenance manifest, avoiding bulk scraping.
1
jorcan
diary
Summarizes daily development progress into project-local and global diary files, then syncs them to Notion and Obsidian.
0 · bundle
brycewang-stanford
fast-workflow
Use when planning a USENIX FAST project timeline from venue fit through choosing a Spring or Fall deadline, double-blind submission, the author-response period, shepherding or a one-shot revision, artifact evaluation, and the open-access camera-ready, with backward-planning offsets tuned to storage evaluation and honest handling of the two-deadline cycle.
1k
gusgad
ralph-wiggum
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.
1
dvy1987
structured-planning
Decompose multi-step work into a revisable subgoal plan with stable step IDs, checkpointing, and plan-ahead execution. Load when a task needs explicit planning before action, subgoal decomposition, plan checkpointing, or ReCAP-style plan-ahead execution. Also triggers on "structured plan", "plan with steps", "subgoal graph", "revise the plan", "checkpoint plan", or multi-step tasks where naive one-shot execution would be fragile. Skips trivial single-step tasks. Pairs with dynamic-routing on failure. Distinct from process-decomposer (registry/triage) and problem-to-plan (doc deliverables).
3 · bundle