How to use
- Copy the installation command and review the source package before installing it in your own agent environment.
- Check the source document for required tools, credentials and supported hosts.
- Describe your input and desired deliverable; review the output against the source material.
npx skills add https://github.com/firegoat-ai/skills --skill linking-to-the-dashboardBefore you start
- Installation does not include a model subscription, API allowance or permission to access your files.
- Repository stars and installation counts describe activity, not an independent quality or security test.
Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.
Linking to the dashboard
Every run, prompt, and trace turn has a canonical dashboard page. When you cite one in an answer, give the full clickable URL — a bare slug or uuid forces the reader to hunt. The base URL is https://2027.dev/evals (BASE_URL in lib/url.ts).
Link formats
With {orgDomain} = the org's domain (e.g. mastra.ai):
- Prompt detail:
https://2027.dev/evals/{orgDomain}/prompts/{promptId}(promptId is a uuid) - Report overview:
https://2027.dev/evals/{orgDomain}/reports/{slug} - Full report:
https://2027.dev/evals/{orgDomain}/reports/{slug}/report - Trace with turn anchor:
https://2027.dev/evals/{orgDomain}/reports/{slug}/trace#turn-{N} - Run status (in-flight):
https://2027.dev/evals/{orgDomain}/runs/{runId} - Org home:
https://2027.dev/evals/{orgDomain}
#turn-N anchors
N is the turn's 1-based `index` field returned by get_trace — NOT the 0-based offset parameter. Don't confuse them.
Screenshot-merge caveat: the dashboard trace page always interleaves browser screenshots into its turn numbering, but get_trace only does that with includeBrowser: true. So for a report that has screenshots, build #turn-N anchors from a trace fetched with includeBrowser: true, or your turn numbers will point at the wrong turns. For runs without screenshots the indices match either way.
Where the ids come from
get_prompt_benchmarksreturnsprompt.{ id, orgDomain }— prompt links are fully constructible.list_prompts/get_promptreturnidbut NOTorgDomain— use the org domain you're operating for (your conversation's org context).list_runs/get_runalready return absoluterunUrl,statusUrl, and (when a report exists)report.url(the dashboard report page) andreport.apiUrl(the REST resource) — prefer those returned URLs over hand-constructing.list_reports/get_report/get_tracereturnslugbut NOTorgDomain— use your conversation's org context for the link.
The org segment must be the canonical org domain that owns the prompt/report — the pages redirect if it's wrong, so use the orgDomain a tool returned (or the returned absolute URL), not a guess.
Practical loop
- Whenever you cite a run, prompt, or trace turn, construct the full URL from the formats above.
- Get
orgDomainfrom the tool response when available, otherwise from your conversation's org context. - Citing evidence from a specific trace turn? Link
.../trace#turn-N(with the screenshot-merge caveat above) so the human lands on the exact moment — this is also how you let them see browser screenshots you can only read as text (see the reading-browser-screenshots skill).
