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...

Security Scan

The skill's claimed purpose (manage and call remote tool libraries via the cogenticlink CLI) aligns with its requirements and instructions; nothing requested or instructed appears disproportionate or unrelated to that purpose.

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.

Assessment

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.

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 <name> <token> [description]

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

3. Remove a library: cogenticlink libraries remove <name>

Executing Tool Calls

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

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

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

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

4. Call a Tool: cogenticlink call <library> <tool> [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 <name> <token> [description]. If the token is unknown, ask the user to create a tool library in Cogentic Hub.
2. Fetch Tool Categories – Run cogenticlink categories <library> 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 <library> <category> to see tools and their tags.
5. Obtain Tool Description (optional) – Run cogenticlink describe <library> <tool> to understand required parameters.
6. Call Tool – Run cogenticlink call <library> <tool> '<json-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 <library>.
4. Invalid parameters – Check the tool's input schema with cogenticlink describe <library> <tool>.