skills/explore-api/SKILL.md
Use when researching an unfamiliar external API before integration to verify feasibility, integration patterns, and limitations
npx skillsauth add giladresisi/ai-dev-env explore-apiInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Systematically research external APIs to prevent integration bugs and validate assumptions before implementation.
Official Documentation
Compatibility Matrix
Community Resources
Endpoint/Feature Support
Authentication & Configuration
Request/Response Formats
Official SDK Usage
Environment Setup
Existing Examples
Create minimal working example to validate understanding:
# Minimal POC to verify API works as expected
# Test: [what this proves]
Expected Outcome: [describe success criteria] Fallback Plan: [alternative if POC fails]
Known Issues
Breaking Changes
Rate Limits & Quotas
Create file: .agents/research/[api-name]-research.md
Contents:
Generate summary block for embedding in plan-feature.md:
## API: [Name] v[Version]
**Documentation:** [Primary URL]
**SDK:** [Library] v[Version] - Compatible: ✓/✗
**Key Findings:**
- Feature [X] supported via [method]
- Event type: [actual name] (not [assumed name])
- Requires: [specific config/setup]
- Limitation: [if any]
**Integration Pattern:**
[Brief code example or reference]
**Validation:**
- [ ] POC tested successfully
- [ ] API key validated
- [ ] Response format verified
What should have been researched:
response.completed (not response.done)end_time parameter in update_run()from langsmith import Client
client = Client()
run_id = uuid.uuid4()
client.create_run(id=run_id, name="test", run_type="llm", inputs={"test": "data"})
client.update_run(run_id=run_id, outputs={"result": "success"}, end_time=datetime.now())
# Verify in dashboard: trace shows SUCCESS status
This research would have prevented:
testing
Creates a new git worktree in the auto-co-trader project for any purpose — optimization, regression, backtesting, brainstorming, etc. Use this skill when the user wants to CREATE or SET UP a new worktree — phrases like "prepare a new worktree", "set up a worktree", "create a new worktree for <purpose>", "prep a new worktree", "new worktree for autoresearch", "prepare optimization from [strategy]", or "create a worktree using [strategy]". Do NOT use this skill when the user is already in a worktree and wants to start/run/begin a task — that is handled by the relevant program file in the worktree session.
development
Use when running comprehensive project validation including tests, type checking, linting, API connectivity checks, and server startup verification
research
Use when performing a meta-level analysis of plan adherence after implementation to identify process improvements and suggest CLAUDE.md updates
documentation
Use when investigating a GitHub issue to identify root cause, assess impact, and create a fix strategy document