How do I install the Herdr Sdk skill?

Run npx skillmds@latest add timmo001/herdr-sdk in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Herdr Sdk safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Herdr Sdk?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Herdr Sdk free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under Apache-2.

Who published Herdr Sdk?

timmo001 (@timmo001) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Herdr Sdk by timmo001 — Agent Skill

Name: Herdr Sdk
Author: timmo001

Herdr Sdk

Use dmmulroy/herdr-ts-sdk (@herdr/sdk) for Effect TypeScript integrations with Herdr. Use when adding, migrating, debugging, or reviewing SDK consumers; read current upstream docs and installed contracts before coding. For terminal or workspace control, use the herdr skill.

timmo001 c3ad62e 2.2 KB Updated Sep 17, 2026

File contents

Herdr SDK

Use @herdr/sdk from dmmulroy/herdr-ts-sdk for Effect integrations. Prefer its supported operations over hand-written socket clients or CLI wrappers. Use the separate herdr skill when operating terminals, panes, tabs, or workspaces as an agent.

Read current docs first. Read the upstream README and package metadata. Follow their current installation and compatibility guidance; do not assume registry availability or reuse remembered API signatures.
Check the consumer. Inspect its manifest, lockfile, installed SDK and Effect packages, overrides, and patches. Establish the resolved SDK revision, public exports, and runtime/Herdr protocol requirements before choosing APIs. Treat declarations or lock entries as unverified installations when packages are absent.
Resolve differences at source. Compare current docs with the installed revision's public source and declarations. Use contracts supported by that consumer; make any required dependency upgrade explicit. Retrieve examples from upstream instead of keeping a copied API reference here.
Keep the integration Effect-native. Apply the effect skill alongside the SDK docs. Compose SDK services and layers at the application boundary, preserve typed failures, and keep streams and resources within their owning scope.
Verify the change. Run the consumer's typecheck and relevant tests against its resolved packages. For live checks, target the intended Herdr server and exercise the changed operation and resource cleanup. Report checked revisions, docs used, and any verification blocked by unavailable dependencies or runtime.

---name: herdr-sdkdescription: Use dmmulroy/herdr-ts-sdk (@herdr/sdk) for Effect TypeScript integrations with Herdr. Use when adding, migrating, debugging, or reviewing SDK consumers; read current upstream docs and installed contracts before coding. For terminal or workspace control, use the herdr skill.license: Apache-2.0---# Herdr SDKUse [`@herdr/sdk` from dmmulroy/herdr-ts-sdk](https://github.com/dmmulroy/herdr-ts-sdk)for Effect integrations. Prefer its supported operations over hand-written socketclients or CLI wrappers. Use the separate `herdr` skill when operating terminals,panes, tabs, or workspaces as an agent.1. **Read current docs first.** Read the upstream [README](https://github.com/dmmulroy/herdr-ts-sdk/blob/main/README.md) and [package metadata](https://github.com/dmmulroy/herdr-ts-sdk/blob/main/package.json). Follow their current installation and compatibility guidance; do not assume registry availability or reuse remembered API signatures.2. **Check the consumer.** Inspect its manifest, lockfile, installed SDK and Effect packages, overrides, and patches. Establish the resolved SDK revision, public exports, and runtime/Herdr protocol requirements before choosing APIs. Treat declarations or lock entries as unverified installations when packages are absent.3. **Resolve differences at source.** Compare current docs with the installed revision's [public source](https://github.com/dmmulroy/herdr-ts-sdk/tree/main/src) and declarations. Use contracts supported by that consumer; make any required dependency upgrade explicit. Retrieve examples from upstream instead of keeping a copied API reference here.4. **Keep the integration Effect-native.** Apply the `effect` skill alongside the SDK docs. Compose SDK services and layers at the application boundary, preserve typed failures, and keep streams and resources within their owning scope.5. **Verify the change.** Run the consumer's typecheck and relevant tests against its resolved packages. For live checks, target the intended Herdr server and exercise the changed operation and resource cleanup. Report checked revisions, docs used, and any verification blocked by unavailable dependencies or runtime.

Frequently asked questions