building-tools SKILL.md skillA
building-tools from celigo/ai is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add celigo/ai/building-tools@git:20261017.e0e159fPins git:20261017.e0e159f in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- celigo/ai
- Path
skills/building-tools/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261017.e0e159f, committed Oct 17, 2026
- First version recorded
- May 20, 2026
- Size
- 21,135 bytes
- Repository stars
- 4
- License
- MIT
Build Celigo tool resources -- reusable building blocks that encapsulate lookups, imports, transforms, and branching behind input/output contracts. Callable from flows, APIs, AI agents, MCP servers, and other tools. Use when creating tools, adding steps, or configuring routing.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
<!-- TIER:1 --> # Building Tools A tool is Celigo's **first-class reusable building block**. It encapsulates logic -- lookups, imports, transforms, branching -- behind a defined input and output contract. Build it once, use it everywhere: from Flows, APIs, AI Agents, MCP Servers, and other Tools. ## Tool Concepts **Why tools exist:** Without tools, users build the same lookup-transform-import patterns repeatedly across Flows, APIs, and Agents. Tools solve this by providing a governed, composable abstraction: one definition, many consumers, consistent behavior. **When to build a tool:** - You're building an **MCP server** -- MCP servers expose tools as endpoints; every piece of logic an MCP server offers must be a tool - The same logic is needed by **2+ consumers** (flows, APIs, agents, MCP servers) -- build once, call everywhere - You want **connection flexibility** -- callers can pass different connections to the same tool definition - You're **composing smaller pieces** -- tools can call other tools for nested orchestration **When NOT to build a tool:** - The logic is **specific to one flow or API and won't be reused** -- inline it as a lookup/import processor directly …
Read the whole file at its exact version.
How to install
mdr add celigo/ai/building-tools@sha256:a07a09d2e97731dfThe line at the top of this page pins the label git:20261017.e0e159f, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_tdk4hlzes3xy3ijs)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between May 20, 2026 and Oct 17, 2026, about one every 37 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261017.e0e159f latest | 2026-10-17 | e0e159f | 21,135 B | A | view · diff |
| git:20260802.64e70c5 | 2026-08-02 | 64e70c5 | 20,883 B | A | view · diff |
| git:20260722.b000fd6 | 2026-07-22 | b000fd6 | 19,557 B | A | view · diff |
| git:20260618.593a4ab | 2026-06-18 | 593a4ab | 14,302 B | A | view · diff |
| git:20260520.7414ff1 | 2026-05-20 | 7414ff1 | 14,298 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (21135 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
celigo/ai · 4 stars · license MIT · pushed 2026-10-20 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_tdk4hlzes3xy3ijs GET https://markdownregistry.com/api/v1/resolve?ref=celigo/ai/building-tools GET https://markdownregistry.com/api/v1/blob/a07a09d2e97731dfc32958cdd1ce1518d0bf648d7038e001876b9ad29282982e
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.