← Back to Skills Marketplace
cogenticlab

Connect Tool Library

by cogenticlab · GitHub ↗ · v2.0.0 · MIT-0
cross-platform ✓ Security Clean
135
Downloads
0
Stars
0
Active Installs
3
Versions
Install in OpenClaw
/install connect-tool-library
Description
Interact with remote tool libraries via cogenticlink CLI. Use this skill when you need to manage Tool libraries (tokens), browse available tools, and execute...
README (SKILL.md)

Connect Tool Library Skill (via cogenticlink CLI)

Managing Tool Libraries (Tokens)

Before using any tool, you must add a library (API token) using the cogenticlink CLI:

  1. Set a library (name, token, optional description): cogenticlink libraries set \x3Cname> \x3Ctoken> [description]

  2. List all libraries (markdown output): cogenticlink libraries

  3. Remove a library: cogenticlink libraries remove \x3Cname>

Executing Tool Calls

All tool commands require the library name as a positional argument.

  1. Fetch Tool Categories (markdown output): cogenticlink categories \x3Clibrary>. Returns a list of categories.

  2. Fetch Tool List of Category (markdown output): cogenticlink list \x3Clibrary>. If category is omitted, defaults to All Tools.

  3. Obtain Tool Description & Input Schema: cogenticlink describe \x3Clibrary> \x3Ctool>. Returns Markdown containing the tool's description and JSON schema for parameters.

  4. Call a Tool: cogenticlink call \x3Clibrary> \x3Ctool> [parameters]. parameters is an optional JSON object (default {}). Successful responses return JSON with a content array. Errors return isError: true with details in content.

Workflow

  1. Check/Create Library – If no library exists, instruct the user to set one: cogenticlink libraries set \x3Cname> \x3Ctoken> [description]. If the token is unknown, ask the user to create a tool library in Cogentic Hub.
  2. Fetch Tool Categories – Run cogenticlink categories \x3Clibrary> to see available categories.
  3. Select a category, If none selected, use All Tools category.
  4. Fetch Tool List from Selected Category – Run cogenticlink list \x3Clibrary> \x3Ccategory> to see tools and their tags.
  5. Obtain Tool Description (optional) – Run cogenticlink describe \x3Clibrary> \x3Ctool> to understand required parameters.
  6. Call Tool – Run cogenticlink call \x3Clibrary> \x3Ctool> '\x3Cjson-params>' to execute.

Troubleshooting with the CLI

  1. Library not found – Run cogenticlink libraries to list existing libraries.
  2. Invalid token – Re‑set the library with the correct token.
  3. Tool not found – Verify the tool name using cogenticlink list \x3Clibrary>.
  4. Invalid parameters – Check the tool's input schema with cogenticlink describe \x3Clibrary> \x3Ctool>.
Usage Guidance
This skill appears coherent and does what it says: it installs the public npm package 'cogenticlink' and uses that CLI to manage and invoke tool libraries. Before installing: (1) review the cogenticlink npm page and package owner to confirm you trust the publisher, (2) inspect the package contents or its GitHub repo if available, (3) be aware that your API tokens will be stored in ~/.cogenticlab/link/config.json (check file permissions and consider using tokens scoped/limited for this purpose), and (4) consider installing/testing the CLI in a sandbox or container if you want to limit risk. If you need higher assurance, provide the repo URL or package tarball for a more detailed review.
Capability Analysis
Type: OpenClaw Skill Name: connect-tool-library Version: 2.0.0 The skill bundle provides a legitimate interface for the 'cogenticlink' CLI to manage and execute remote tools from the Cogentic Hub. The instructions in SKILL.md guide the agent through standard operations such as token management, tool discovery, and parameter validation, with no evidence of malicious intent, data exfiltration, or prompt injection attacks.
Capability Assessment
Purpose & Capability
The name, description, required binaries (node, npx), the npm package install (cogenticlink), and the required config path (~/.cogenticlab/link/config.json) all line up with a CLI-based tool-library manager. There are no unrelated credentials or binaries requested.
Instruction Scope
SKILL.md contains concrete CLI commands limited to cogenticlink (libraries set/list/remove, categories, list, describe, call). It does not instruct reading unrelated system files or environment variables. Note: the CLI will read/write the stated config path and perform network calls to the service (expected for this purpose).
Install Mechanism
The install spec pulls a public npm package ('cogenticlink') which is a common and expected mechanism for a Node CLI. This is moderate-risk relative to an instruction-only skill because it installs code from npm; however the package is referenced on npm (not an arbitrary URL) which is proportionate to the stated purpose.
Credentials
No environment variables or external credentials are requested by the skill. The skill expects a config file in the user's home directory where API tokens are stored; that is appropriate for a CLI that manages libraries/tokens, but those tokens are sensitive and will reside on disk.
Persistence & Privilege
always is false and the skill does not request elevated/system-wide privileges or modify other skills' configs. Autonomous invocation is allowed (default) but not combined with any broad or unexplained access.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install connect-tool-library
  3. After installation, invoke the skill by name or use /connect-tool-library
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v2.0.0
**Major update: HTTP API interaction replaced with cogenticlink CLI** - Now uses the cogenticlink CLI (Node.js) instead of curl and direct HTTP requests. - Tool library (token) management is handled via CLI commands: add, list, and remove libraries. - Tool browsing and execution are performed with cogenticlink subcommands (`categories`, `list`, `describe`, `call`). - Credentials are stored in `~/.cogenticlab/link/config.json` instead of a markdown file. - Updated troubleshooting steps and workflow to reflect CLI usage.
v1.1.0
connect-tool-library 1.0.1 - Updated tool list and description endpoints to use empty string ("") instead of empty JSON as the request body. - Simplified the tool list markdown output format. - Removed logic for retrieving API tokens from environment variables; tokens are now retrieved exclusively from the credentials file. - Minor documentation clarifications in workflow and endpoint usage.
v1.0.0
Initial release of connect-tool-library. - Interact with remote tool libraries via HTTP API for tool discovery and usage. - Manage and store HTTP API credentials securely in a config file. - Browse available tool categories and lists, fetch tool descriptions, and execute remote tool calls. - Automated handling of API token retrieval from file or environment variable. - Consistent error handling with clear response formats.
Metadata
Slug connect-tool-library
Version 2.0.0
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 3
Frequently Asked Questions

What is Connect Tool Library?

Interact with remote tool libraries via cogenticlink CLI. Use this skill when you need to manage Tool libraries (tokens), browse available tools, and execute... It is an AI Agent Skill for Claude Code / OpenClaw, with 135 downloads so far.

How do I install Connect Tool Library?

Run "/install connect-tool-library" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Connect Tool Library free?

Yes, Connect Tool Library is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Connect Tool Library support?

Connect Tool Library is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Connect Tool Library?

It is built and maintained by cogenticlab (@cogenticlab); the current version is v2.0.0.

💬 Comments