메뉴
Activate when user needs multi-URL scraping, browser automation pipelines, or efficient tool orchestration to reduce API round-trips and context usage.
Language-agnostic API design patterns covering REST and GraphQL, including resource naming, HTTP methods, status codes, versioning, pagination, filtering, authentication, error handling, and schema design. Activate when working with APIs, REST endpoints, GraphQL schemas, API documentation, OpenAPI/Swagger, JWT, OAuth2, endpoint design, API versioning, rate limiting, or GraphQL resolvers.
Git workflow and commit guidelines. Trigger keywords: git, commit, push, .git, version control. MUST be activated before ANY git commit, push, or version control operation. Includes security scanning for secrets (API keys, tokens, .env files), commit message formatting with HEREDOC, logical commit grouping (docs, test, feat, fix, refactor, chore, build, deps), push behavior rules, safety rules for hooks and force pushes, and CRITICAL safeguards for destructive operations (filter-branch, gc --prune, reset --hard). Activate when user requests committing changes, pushing code, creating commits, rewriting history, or performing any git operations including analyzing uncommitted changes.
Testing workflow patterns and quality standards. Activate when working with tests, test files, test directories, code quality tools, coverage reports, or testing tasks. Includes zero-warnings policy, targeted testing during development, mocking patterns, and best practices across languages.
Ansible automation workflow guidelines. Activate when working with Ansible playbooks, ansible-playbook, inventory files (.yml, .ini), or Ansible-specific patterns.
Claude Code AI-assisted development workflow. Activate when discussing Claude Code usage, AI-assisted coding, prompting strategies, or Claude Code-specific patterns.
Guidelines for containerized projects using Docker, Dockerfile, docker-compose, container, and containerization. Covers multi-stage builds, security, signal handling, entrypoint scripts, and deployment workflows.
| name | ptc-orchestration |
| description | Activate when user needs multi-URL scraping, browser automation pipelines, or efficient tool orchestration to reduce API round-trips and context usage. |
Use Programmatic Tool Calling (PTC) for efficient multi-tool workflows. PTC allows Claude to write Python code that orchestrates multiple tool calls, reducing:
Activate this skill when the user needs:
# Multi-URL scraping with summarization
python -m ptc_wrapper.cli scrape https://url1.com https://url2.com
# Browser automation pipeline
python -m ptc_wrapper.cli browser "Navigate to X, extract Y" --url https://start.com
# Custom PTC prompt
python -m ptc_wrapper.cli run "Your complex multi-tool task" --servers flaresolverr,browsermcp
# List available tools
python -m ptc_wrapper.cli list --tools
from ptc_wrapper import PTCClient
async with PTCClient() as client:
await client.load_mcp_servers(["flaresolverr"])
result = await client.scrape_urls(urls, summarize=True)
Ensure the wrapper is installed:
cd ~/.claude/tools/ptc-wrapper
uv pip install -e .
allowed_callers to enable code executionPTCClient → Anthropic API (with code_execution)
↓
MCPClient → MCP Servers (flaresolverr, browsermcp via stdio)
The wrapper adds:
code_execution_20250825 tool to enable PTCallowed_callers: ["code_execution_20250825"] to each toolinput_examples for parameter accuracyadvanced-tool-use-2025-11-20