tribunal

Tensorlake SDK — sandboxes for AI agents and applications. Use when the user mentions tensorlake or sandboxes, or asks about Tensorlake APIs/docs/capabilities. Also use when building an application, coding agent, or agentic system that needs a sandbox to run code — e.g., executing LLM-generated or untrusted code, persistence via suspend/resume, snapshots/checkpoints for forking parallel workers, custom images, exposing ports, egress allowlists, PTY/interactive shells, computer-use / desktop automation, browser automation (Chrome CDP, Playwright), local tunnels for non-HTTP protocols, async parallel sandboxes, Harbor evals or RL rollouts, file transfer, SSH access, remote-dev (VS Code Remote-SSH), or OCI base images. Also covers Tensorlake's sandbox-native durable workflow orchestration. Works alongside any LLM provider (OpenAI, Anthropic), agent framework (Claude/OpenAI agents SDK, LangChain), database, or API. When this skill applies, ALWAYS WebFetch https://docs.tensorlake.ai/llms.txt first.

Ship Tribunal to production and triage deployment, health-check, Fly, Neon, GitHub OAuth/App, Tensorlake, proxy, review-engine, or live-review rollout issues. Use when a user asks to deploy Tribunal, prepare production secrets, verify production readiness, enable live reviews, debug broken deploys, inspect production health, or recover/rollback Tribunal services.

Ship Tribunal to production and triage deployment, health-check, Fly, Neon, GitHub OAuth/App, Tensorlake, proxy, review-engine, or live-review rollout issues. Use when a user asks to deploy Tribunal, prepare production secrets, verify production readiness, enable live reviews, debug broken deploys, inspect production health, or recover/rollback Tribunal services.

Address unresolved GitHub pull request review comments by analyzing feedback, implementing fixes, and resolving threads.

Generate or refresh a multi-agent project context document and execution-plan authoring prompt from repository analysis. Use when bootstrapping multi-agent orchestration, updating architecture/ownership/contracts guidance, or preparing a reusable planning prompt. Support explicit output path (`OUTPUT=<path>` or plain-language path request); otherwise detect a sensible default path from the project structure.

Stage intended changes, validate them, and create a focused commit with a clear, ticket-aware message.

Apply frontend domain conventions for components, Svelte runes/attachments, route form UX, and testing patterns.

Create or update a GitHub pull request with ticket context, synchronized branch history, and a concrete test plan.

Operate and validate PostgreSQL/Drizzle workflows for schema migrations, query design, indexing, Neon constraints, and performance diagnostics.

Deeply analyze one or more existing Linear tickets through codebase exploration, domain expert consultation, and junior engineer validation, then write comprehensive implementation plans directly into each ticket's Linear description.

Read PLAN.md, create an agent team, and execute the implementation plan using recommended subagents.

Apply GitHub integration domain rules for webhooks, API patterns, OAuth integrations, and CI workflow safety.

Promote learning markdown files into durable project documentation and delete processed learning files. Use when `documentation/learnings/*.md` has entries that should update canonical domain skills (`component-standards`, `database-operations`, `github-integration-rules`, `markdown-security`), other `.claude/skills/**/SKILL.md`, `.claude/rules/*.md`, `AGENTS.md`, `CLAUDE.md`, `README.md`, and other `README.md` files.

Fix ESLint, TypeScript, and formatting issues in the codebase through iterative error resolution.

Canonical markdown security domain pack. Apply secure markdown rendering patterns when modifying src/lib/markdown; prevents XSS through proper sanitization and unified.js phase handling.

Rebase the current git branch on origin/main, integrate any upstream branch commits, and push updated history safely. Use when you need to sync a feature branch with main and its remote tracking branch before continuing work or opening a PR.

Generate or refresh a multi-agent project context document and execution-plan authoring prompt from repository analysis. Use when bootstrapping multi-agent orchestration, updating architecture/ownership/contracts guidance, or preparing a reusable planning prompt. Support explicit output path (`OUTPUT=<path>` or plain-language path request); otherwise detect a sensible default path from the project structure.

Apply frontend domain conventions for components, Svelte runes/attachments, route form UX, and testing patterns.

Deeply analyze one or more existing Linear tickets through codebase exploration, domain expert consultation, and junior engineer validation, then write comprehensive implementation plans directly into each ticket's Linear description.

Apply GitHub integration domain rules for webhooks, API patterns, OAuth integrations, and CI workflow safety.

Promote learning markdown files into durable project documentation and delete processed learning files. Use when `documentation/learnings/*.md` has entries that should update canonical domain skills (`component-standards`, `database-operations`, `github-integration-rules`, `markdown-security`), other `.claude/skills/**/SKILL.md`, `.claude/rules/*.md`, `AGENTS.md`, `CLAUDE.md`, `README.md`, and other `README.md` files.

Canonical markdown security domain pack. Apply secure markdown rendering patterns when modifying src/lib/markdown; prevents XSS through proper sanitization and unified.js phase handling.