skillZs
★ LIVE SKILL TAGS ★
>>> LIVE SKILLS INDEX <<<
* OPEN SOURCE *
NO LOGIN, NO TRACKING
※ REAL INSTALL DATA ※
← back to all skills
docs.trajectory.ai63 installs

trajectory

Use the Trajectory SDK to integrate specs (benchmarks), evaluate or train models, inspect run results, and serve checkpoints.

How do I install this agent skill?

npx skills add https://docs.trajectory.ai --skill trajectory
view source ↗

Is this agent skill safe to install?

No partner audit is available yet. Read the source before installing.

What does this agent skill do?

Trajectory

Follow the customer's requested scope. Evaluation alone does not authorize training or deployment. Preserve the source spec's solving and grading behavior. If credentials are missing, finish the offline work and state what remains unverified.

Connect and find the contract

Use the latest trajectory-sdk compatible with project dependency constraints. Import Client from trajectory; it reads TRAJECTORY_API_KEY and TRAJECTORY_BASE_URL, or uses a saved tj login profile. Run tj whoami --json to confirm the organization before creating resources. If authentication is missing, ask the user to complete tj login --no-browser; never ask them to paste a secret into the conversation. Do not wait for interactive input inside ordinary commands. Use --json and --non-interactive for automation. Discover commands and schemas with tj schema --json and bundled guidance with tj docs --json.

Use the project's Python environment for SDK calls and guide discovery (for example, uv run python in a uv project). The installed SDK's signatures and bundled guides are the API contract; do not assume this skill's installation upgraded that SDK. Find the bundled docs directory (it holds agent.mdx, platform.mdx, and guides/) in the directory field of tj docs --topic index --json. This works in both wheel and editable SDK installs. If a guide this skill names is missing there, the installed SDK predates it: upgrade trajectory-sdk within the project's constraints, or read the guide at https://docs.trajectory.ai/<path> (for example, guides/images.mdx is /guides/images). Use the installed CLI command supplied in the onboarding prompt when tj is not on PATH. The cookbook offers worked examples.

Link what you report

When a resource is created, share its ID and a labeled platform link before waiting. Include links in progress updates and when pointing to a resource in a next step. When work finishes, report its outcome and link again. Link the evidence behind results or failures: a selected trajectory, training step, comparison, or deployed model. Place links beside the relevant claim; use the run link when a more specific selection is unavailable.

Use PlatformLinks from trajectory.lib.platform_links; see bundled platform.mdx. Use PlatformLinks(organization_key) with the verified organization key, or PlatformLinks.from_client(client) to look it up once. Links default to https://platform.trajectory.ai. For internal staging or local development, use the API and platform URLs supplied by the setup prompt. Never invent hosts or IDs or include credentials in URLs. If a link cannot be constructed, report the ID and the missing context.

Distinguish submitted, running, successful, failed, and unverified work. State what the human can inspect or decide next. Local-only findings need no platform link.

Integrate a spec

Read the bundled agent.mdx and guides/spec.mdx. Adapt examples to the source spec's tasks, tools, and scoring. For an existing scorer, Inspect harness, or diagnostic files, read guides/source-graders.mdx, guides/inspect.mdx, or guides/diagnostic-artifacts.mdx. If the source task shows the model images, read guides/images.mdx and pick a model whose input_modalities includes image.

Trace the source task loader, actor and tools, grader, and result reader. Preserve their inputs, call order, state, and primary score. Keep private grader inputs, answers, and credentials outside actor-visible tools; check what those tools can access.

  • Reuse a suitable agent and spec before creating another. Keep source task IDs and splits when selecting a subset. Register a revised harness under the same spec name and retain its new bench_id.
  • Route managed model calls to the selected actor. Keep source-fixed judges separate from that actor. Use SecretRef for runtime credentials.
  • Publish the score the source result reader uses. Keep other scores as named components when useful; a fallback from an unrun grader is not a grade.
  • Report the actual ending. Check finish_reason before tool dispatch; a length-capped answer is TRUNCATION even when the source grades it. A clean process exit alone does not establish ENV_DONE. Read guides/termination-reasons.mdx for other endings.

Save runnable uploader and runtime entrypoints in the customer's repo. Check packaged imports and representative correct, wrong, cut-off, and error cases. Run a one-task managed diagnostic or eval, with the model and options you will train with, before scaling up; check each task's ending and reward and the source tools and grader, not only the image build or aggregate score.

Evaluate or train

Read the bundled guides/evaluations.mdx or guides/training.mdx as needed. Check supported models and options, preserve source generation settings through the run's options (they override request values in managed runs), and budget for grading. Before training, check eligible endings and the planned sample budget. Watch attempted and graded rollouts and optimizer progress; stop a validation run that exceeds its planned budget without progress.

Compare baseline and checkpoint on the same spec version, held-out tasks, scorer, and effective settings. Report attempted, graded, failed, and unfinished counts before interpreting means. Check native grades and whether an optimizer update occurred before attributing a score change to training. A smoke eval does not establish improvement.

Serve a checkpoint or capture application traffic

Read the bundled guides/deployments.mdx. Verify a completed, nonempty answer, and remove temporary deployments when finished. Promoting an active production model requires the customer's authorization. For application traffic, see guides/production-traces.mdx (private beta) and retain the request's trajectory ID. To download a checkpoint's weights, read guides/checkpoint-downloads.mdx (private beta).

Inspect or recover a run

Read the bundled reference/troubleshooting.mdx; search it for the error text or symptom.

Use the saved operation or run ID. After a local timeout, retrieve that remote operation before creating another; stopping a client does not cancel its run. Never complete a trajectory owned by a live worker.

Locate the failure in the build, runtime, model, harness, grader, reward publication, or aggregation. Read available logs or artifacts. For flat rewards, distinguish wrong answers from absent grades, rejected endings, and no training progress.

Report observed evidence with resource IDs and links. Do not guess an unavailable failure reason. Repeat the affected validation after a fix and confirm requested remote cancellation or cleanup.

For authorized Trajectory feedback—including suggestions, positive observations, and friction—follow the agent-feedback skill.

Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.

<a href="https://skillzs.dev/skills/docs.trajectory.ai/trajectory">View trajectory on skillZs</a>