菜单
Context about the tools system architecture in seer. Use when understanding BaseTool, tool registry, execution patterns, or debugging tool issues.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
use when creating or updating end-to-end tests for the Seer application. This skill provides guidance on how to structure and implement e2e tests effectively.
React Flow best practices for workflow canvas in seer-frontend. Use when modifying WorkflowCanvas, adding new block types, debugging node rendering issues, or optimizing React Flow performance.
Apply Seer design system patterns when creating or modifying UI components. Auto-triggers for badge, button, input, and form components in src/components/.
Use this when you are asked to debug production errors
Guide for adding new external integrations (OAuth or API key-based) to seer. Use when implementing new service integrations like Google, GitHub, Slack, etc.
Context about runtime credential resolution in seer. Use when understanding how OAuth tokens, resources, and secrets are resolved for tool execution.
| name | tools-creation |
| description | Context about the tools system architecture in seer. Use when understanding BaseTool, tool registry, execution patterns, or debugging tool issues. |
| allowed-tools | Read, Grep, Glob |
Extensible framework for integrating external services with workflows.
register_tool() at import time → _TOOL_REGISTRY[name] = tool → execute_tool() called by workflow runtime → CredentialResolver.resolve() (OAuth lookup, token refresh, resource binding, secrets) → tool.execute(access_token, arguments, credentials)
src/seer/tools/base.py)| Attribute | Purpose |
|---|---|
name / description | Identifier + human label |
required_scopes / provider | OAuth scopes + provider name |
integration_type | Category (e.g. "gmail") |
required_secrets / default_resource | Secrets + auto-resolved resource |
Key methods: execute() (required), get_parameters_schema(), get_resource_pickers(), get_output_schema(), get_metadata().
Structure: src/seer/tools/ → base.py · executor.py · __init__.py · google/ (GoogleAPIClient) · github/ · discord/ (DiscordAPIClient) · supabase/. Tools auto-register at module level via register_tool(MyTool()); import in __init__.py triggers it. Idempotent.
GoogleAPIClient / DiscordAPIClient abstract provider-specific HTTP boilerplatetool.provider → tool.integration_type → OAuth connection → resource bindingexecute(access_token, arguments, credentials=None) exposes resource + secrets| File | Purpose |
|---|---|
src/seer/tools/base.py | BaseTool, registry functions |
src/seer/tools/executor.py | execute_tool() |
src/seer/tools/__init__.py | Tool import/registration |
src/seer/tools/google/base.py | GoogleAPIClient |
src/seer/tools/discord/base.py | DiscordAPIClient |
/credential-resolution · /resource-browser · /add-integration