agentleFS
Sign inStart free
NeoVandNeoVand/op-xy-agent/.agents/skills/langchain-typescript-quickstart/SKILL.md

langchain-typescript-quickstart

Skill1 starsChanged 49 days agoMITView on GitHub

Scaffold a minimal local LangChain agent in TypeScript by following the official quickstart. Use when the user wants to quickly build or try a LangChain agent locally.

  • Reads credentials

3 other projects use a version of this, 1 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 1 is distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Follow the live docs — do not invent an alternate API from memory:

    line 8
  2. Very specific:

    Create a new directory (e.g.

    line 24
  3. Very specific:

    Only secret: the provider API key in .env (gitignored).

    line 26
  4. Very specific:

    Run the example, show output, then stop.

    line 30

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

LangChain TypeScript quickstart

Follow the live docs — do not invent an alternate API from memory:

https://docs.langchain.com/oss/javascript/langchain/quickstart

Fetch that page (Docs MCP or HTTP) and implement what it shows (weather agent + createAgent). Requires Node 22+.

Local setup constraints

Apply these on top of the quickstart (they keep setup minimal and model-agnostic):

  1. Ask which provider/model to use. Showcase that LangChain is model-agnostic. Suggested prompt:

    Which model should this agent use? Pass a provider:model string — e.g. openai:gpt-5.5, anthropic:claude-sonnet-5, google-genai:gemini-2.5-flash-lite. Default if you're unsure: anthropic:claude-sonnet-5.

    Swap the quickstart's model string for their choice (or the default).

  2. Create a new directory (e.g. langchain-agent/) and do all work there — do not pollute the open project.
  3. Only secret: the provider API key in .env (gitignored). No LangSmith / Tavily unless they ask. Prefer they edit .env themselves — don't paste keys into chat.
  4. Install the provider package needed for their model if the quickstart's base install isn't enough.
  5. Run the example, show output, then stop. Point to langchain-fundamentals for next steps.

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.

Check your setup, free