agentleFS
madanlalitmadanlalit/agentskills/langsmith-fetch/SKILL.md

langsmith-fetch

Skill1 starsChanged 5 months agoMITView on GitHub

Fetch and inspect LangSmith traces and threads with the langsmith-fetch CLI. Use when a user asks to pull recent traces/threads, fetch a specific trace/thread by ID, export LangSmith data to JSON files, filter by project or time window, or produce raw JSON output for downstream analysis/automation.

  • Reads credentials

31 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use connect-apps, twitter-algorithm-optimizer and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • ArogyaReddySkill

    connect-apps

    Connect Claude to external apps like Gmail, Slack, GitHub. Use this skill when the user wants to send emails, create issues, post messages, or take actions in external services.

    Also in 18 projects that use this

  • trendinuxSkill

    twitter-algorithm-optimizer

    Analyze and optimize tweets for maximum reach using Twitter's open-source algorithm insights. Rewrite and edit user tweets to improve engagement and visibility based on how the recommendation system ranks content.

    Also in 15 projects that use this

  • ArogyaReddySkill

    skill-share

    A skill that creates new Claude skills and automatically shares them on Slack using Rube for seamless team collaboration and skill discovery.

    Also in 18 projects that use this

  • ComposioHQSkill

    agent-deep-links

    Build, validate, and troubleshoot deep links for Codex, Cursor, VS Code, Visual Studio, and similar tools. Use when users ask for clickable links (especially in Slack) that open threads, files, folders, or app settings.

    Also in 3 projects that use this

  • ComposioHQSkill

    helium-mcp

    Search real-time news with bias scoring, get live stock/ETF/crypto data with AI analysis, ML options pricing, balanced news synthesis, and meme search via the Helium MCP server.

    Also in 3 projects that use this

  • +1 more from ComposioHQ
  • +6 more from ArogyaReddy

The file

Show its rules and text

We split this skill into the rules it gives an agent

16 rules. 0 are common, 7 are distinctive, and 9 are very specific to this project.

  • 0

    Common

    Most of the 31 edited versions we read keep these.

  • 7

    Distinctive

    This author's own choices. Worth a look.

  • 9

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Prefer directory-mode bulk export, switch to stdout only when explicitly requested, and use --format raw when machine parsing stdout.

    line 9
  2. Distinctive:

    Verify the CLI is installed:

    line 13
  3. Very specific:

    Use langsmith-fetch trace <trace-id> for one trace.

    line 31
  4. Very specific:

    Use langsmith-fetch thread <thread-id> for one thread.

    line 32
  5. Very specific:

    Use langsmith-fetch traces <output-dir> for many traces.

    line 33
  6. Very specific:

    Use langsmith-fetch threads <output-dir> for many threads.

    line 34
  7. Very specific:

    Treat --project-uuid as required for thread operations unless a valid value is already configured.

    line 36
  8. Distinctive:

    Default to directory mode for bulk commands:

    line 40
  9. Distinctive:

    Use stdout mode only when the user explicitly asks for terminal output or piping.

    line 45
  10. Very specific:

    Use --format raw in stdout mode when output is consumed by tools/agents.

    line 46
  11. Very specific:

    Avoid adding --format in directory mode unless requested.

    line 47
  12. Very specific:

    Use --file for single output artifacts when the user wants one file.

    line 48
  13. Distinctive:

    Call out if zero results were returned due to filters.

    line 83
  14. Distinctive:

    Do not invent trace IDs, thread IDs, or project UUIDs.

    line 92
  15. Distinctive:

    Ask for missing IDs only when they cannot be inferred from config or prior context.

    line 93
  16. Distinctive:

    Keep bulk fetch limits reasonable unless the user requests larger exports.

    line 94

“Common” is measured: kept by at least 6 in 10 of the 31 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

LangSmith Fetch

Fetch LangSmith traces and threads through langsmith-fetch with reliable defaults for debugging and automation. Prefer directory-mode bulk export, switch to stdout only when explicitly requested, and use --format raw when machine parsing stdout.

Preflight (required)

  1. Verify the CLI is installed:
command -v langsmith-fetch
  1. Inspect current config:
langsmith-fetch config show
  1. Set/verify environment variables when needed:
export LANGSMITH_API_KEY=lsv2_...
export LANGSMITH_PROJECT=your-project-name
export LANGSMITH_ENDPOINT=https://api.smith.langchain.com
  1. Edit ~/.langsmith-cli/config.yaml directly if configuration changes are needed and no config write subcommand is available in the installed CLI.

Pick the right command

  • Use langsmith-fetch trace <trace-id> for one trace.
  • Use langsmith-fetch thread <thread-id> for one thread.
  • Use langsmith-fetch traces <output-dir> for many traces.
  • Use langsmith-fetch threads <output-dir> for many threads.
  • Pass --project-uuid <uuid> whenever project scope may be ambiguous.
  • Treat --project-uuid as required for thread operations unless a valid value is already configured.

Apply output-mode rules

  • Default to directory mode for bulk commands:
langsmith-fetch traces ./out/traces --limit 10
langsmith-fetch threads ./out/threads --limit 10
  • Use stdout mode only when the user explicitly asks for terminal output or piping.
  • Use --format raw in stdout mode when output is consumed by tools/agents.
  • Avoid adding --format in directory mode unless requested; the CLI ignores it and warns.
  • Use --file for single output artifacts when the user wants one file.

Use core recipes

Fetch one trace in raw JSON:

langsmith-fetch trace <trace-id> --format raw

Fetch one thread in raw JSON with explicit project:

langsmith-fetch thread <thread-id> --project-uuid <project-uuid> --format raw

Fetch recent traces by time window into a directory:

langsmith-fetch traces ./out/traces --limit 25 --last-n-minutes 60 --project-uuid <project-uuid>

Fetch recent threads since timestamp:

langsmith-fetch threads ./out/threads --since 2026-01-01T00:00:00Z --project-uuid <project-uuid>

Customize filenames in directory mode:

langsmith-fetch traces ./out/traces --limit 20 --filename-pattern "trace_{index:03d}_{trace_id}.json"

Report results clearly

  • Report the exact command used.
  • Report where files were written.
  • Report how many files were produced.
  • Provide one sample file path to confirm output shape.
  • Call out if zero results were returned due to filters.

References

Load only when needed:

  • references/cli-recipes.md for command cookbook and troubleshooting.

Guardrails

  • Do not invent trace IDs, thread IDs, or project UUIDs.
  • Ask for missing IDs only when they cannot be inferred from config or prior context.
  • Keep bulk fetch limits reasonable unless the user requests larger exports.
  • Preserve original JSON payloads; do not rewrite fetched files unless requested.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.