tools-creation

Document Seer tool registration, credential resolution, and runtime execution patterns.

5|1|Updated Oct 14, 2025
One-click install
npx skills add https://github.com/seer-engg/seer --skill tools-creation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tools-creation
Source: https://github.com/seer-engg/seer/tree/main/.claude/skills/tools-creation
Command: npx skills add https://github.com/seer-engg/seer --skill tools-creation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Document the Seer tools system architecture, including registration, credential resolution, and execution patterns, to aid understanding and debugging of tool integrations.

Core Features & Use Cases

  • Tool Registration and Registry: explains the import-time registration pattern and global registry.
  • Credential Resolution & Execution: covers how credentials are resolved and passed to tools during runtime, including potential integration with token refresh and resource binding.
  • Workflow Integration: describes how tools are invoked by the workflow runtime and how provider/base classes standardize behavior.
  • Use Case: debugging a tool integration or adding a new tool to the registry.

Quick Start

Describe how to add a new tool to the registry and invoke it within a workflow.

Frequently Asked Questions about tools-creation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How does tool registration work in the Seer platform?

Tool registration in Seer uses an import-time registration pattern that automatically populates a global registry, allowing software engineers to discover and invoke tools within workflows without manual setup.

How are credentials resolved and passed to tools during workflow execution?

Credential resolution occurs at runtime, dynamically binding tokens and resources to tools before execution, including handling token refresh and resource binding to ensure authenticated workflow execution.

How do I add a new tool to the registry and invoke it in a workflow?

To add a new tool, implement the required class interfaces and provider base classes to standardize behavior, then register it via the import-time pattern so the workflow runtime can invoke it.

What class interfaces are required for extending tool integrations?

Extending tool integrations requires implementing specific provider and base classes that standardize execution behavior, credential resolution, and workflow runtime invocation across the Seer platform.

Why is my tool integration failing during workflow execution?

Workflow execution failures often stem from incorrect credential resolution, missing import-time registration in the global registry, or unimplemented base class interfaces required by the workflow runtime.

Does the Seer tools system support token refresh for tool execution?

Yes, credential resolution during tool execution integrates with token refresh mechanisms, ensuring that expired credentials are dynamically updated before the workflow runtime invokes the tool.