Share agent traces to open datasets on HuggingFace Hub. Use this skill when the user mentions OpenTraces, trace capture, Trace Trails, workflow-built datasets, dataset review, or publishing reviewed dataset rows.
Share agent traces to open datasets on HuggingFace Hub. Use this skill when the user mentions OpenTraces, trace capture, Trace Trails, workflow-built datasets, dataset review, or publishing reviewed dataset rows.
Project already-captured traces into scored-rollout rows for the SkillOpt optimizer.
Per-commit trace lineage rows for a branch context, deterministic.
Derive compact eval rows from command-attributed trace trajectories.
Land every site-related fix on main, deploy opentraces.ai to Vercel production, and verify it works across all pages (desktop + mobile) and the email-capture flow, fixing and re-deploying until green. Runs as a goal: land -> deploy -> verify -> triage -> repeat until safe. Use when the user says "deploy site", "deploy to vercel", "push site", "ship the site", "deploy-site", or "land and verify the site". For a full coordinated release that also bumps the version and publishes the Python packages, use /release-pack instead.
Take one or more GitHub issues and drive each to a review-ready pull request, holding one belief throughout: an issue is a hypothesis, not a spec. The pipeline VERIFIES BEFORE IT TRUSTS and runs TWO ADVERSARIES before it commits: multi-agent investigation of the real cause (flagging any "landmine" — a cited function or file:line that does not exist) and the blast radius, a plan whose test must go RED BEFORE GREEN, two adversarial gates on that plan (a self/ethos checklist + a pure codex adversarial pass), implementation expressed as a forged `/goal` (via goal-forge) whose verify loop runs the otbox acceptance journey, a green suite + docs sync, a PR that `Closes #<n>`, and a FINAL codex adversarial review of the diff. Honesty, not theater: it reports unmet acceptance criteria and invalid issues rather than faking a fix. The human merges. Everything happens in a per-issue git worktree; multiple issues each get their own worktree + branch + PR. Use when the user says "issue-to-pr", "solve issue", "fix issue #N"
Synchronize all documentation surfaces after code changes. Use when the user says "docs-update", "update docs", "sync docs", "update references", "docs are stale", or after any significant code change (CLI commands, schema fields, install methods, new features). This skill catches stale references across 50+ files: marketing site, mkdocs pages, llms.txt, the agent skill, CLI help text, viewer UI, and READMEs. Proactively suggest this after merging features or changing CLI surface.