api-use-external
Any time an external api needs to be understood or queried
Best use case
api-use-external is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Any time an external api needs to be understood or queried
Teams using api-use-external should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/api-use-external/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How api-use-external Compares
| Feature / Agent | api-use-external | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Any time an external api needs to be understood or queried
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# External API use
Includes how to query and process the current existing external APIs:
- IMDb Primary API.
- IMDb Fallback API - To be used when IMDb primary API times out or is otherwise unreachable.
## Index
- **API configuration**:
- **API provider framework**:
- **Docs and examples**: documenation, endpoints, and request/response examples for both IMDb Primary API and IMDb Fallback API.
## API configuration
- All API settings such as keys, base URLs, and timeouts come from `config.py`.
- API credentials and other secrets come from `.env`.
## API provider framework
### API integration
- IMDb integration must remain active and fully operational.
- Core implementation is in `utils/imdb_core.py` using RapidAPI-based providers.
- Core function families include `imdb_details_fetch_core`, `imdb_search_core`, `imdb_rating_core`, `imdb_import_core`, `imdb_api_search_title`, and `imdb_api_get_details`.
- Provider configuration switches are defined in `config.py`:
- `MEDIA_ENABLE_IMDB = True` must remain enabled.
### Base API provider
- `utils/api_provider_core.py` defines `BaseApiProvider` for all external HTTP APIs.
- Handles HTTP requests, authentication, token management, error handling, and response normalization.
- Stateless by design with no Flask context; safe to use in core modules.
- Includes retry strategy and standardized response format.
- Use this class instead of creating custom HTTP client code per API.
### Provider descriptors
- `utils/api_provider_descriptors.py` defines configuration descriptors for each external API.
- New providers should be added by defining a descriptor in this module, not by creating new ad-hoc client modules.
- Descriptors capture base URL, authentication strategy, header builders, and normalization callbacks.
- Supports bearer tokens, API keys, and static tokens.
- Includes `TokenCache` for automatic token refresh and caching where needed.
### Core vs presentation for APIs
- Core API logic belongs in `utils/*_core.py` modules that use BaseApiProvider and descriptors.
- Flask-aware presentation logic belongs in `routes/utils_*.py` modules that call core functions.
- Keep API core code free of Flask imports and request context.
## Docs and examples
- **IMDb primary API**: `utils/imdb-01-docs.md` (IMDb236 API)
- **IMDb fallback API**: `utils/imdb-02-docs.md` (IMDb8 API)
## Legacy unused but saved
**Do not use or enable but do save**:
- TVDB and TMDB are not currently enabled in the application.
- Supporting code and tests exist but must remain disabled unless explicitly authorized.
- Residual assets include templates under `templates/admin`, JavaScript under `static/js`, and utilities under `utils/api_tvdb` and `utils/api_tmdb`.
- Runtime disabling is enforced in routes and config.
- Presence does not imply enablement; do not enable or delete them without approval.
- Provider configuration switches are defined in `config.py`:
- `MEDIA_ENABLE_TVDB = False` must stay disabled for now.
- `MEDIA_ENABLE_TMDB = False` must stay disabled for now.Related Skills
external-perspectives
Curated community patterns and alternative approaches from AI-assisted development ecosystem. Auto-activates when users ask about workflow patterns, context management techniques, or alternative prompting strategies. Provides external validation and inspiration.
External KI Integration
Skill for accessing external AI services (ChatGPT, Claude, Hugging Face, etc.) via browser automation (Chrome Relay) and APIs to assist with tasks.
moodle-external-api-development
Create custom external web service APIs for Moodle LMS. Use when implementing web services for course management, user tracking, quiz operations, or custom plugin functionality. Covers parameter va...
bgo
Automates the complete Blender build-go workflow, from building and packaging your extension/add-on to removing old versions, installing, enabling, and launching Blender for quick testing and iteration.
nextjs-shadcn-builder
Build new Next.js applications or migrate existing frontends (React, Vue, Angular, vanilla JS, etc.) to Next.js + shadcn/ui with systematic analysis and conversion. Enforces shadcn design principles - CSS variables for theming, standard UI components, no hardcoded values, consistent typography/colors. Use for creating Next.js apps, migrating frontends, adopting shadcn/ui, or standardizing component libraries. Includes MCP integration for shadcn documentation and automated codebase analysis.
nextjs-senior-dev
Senior Next.js 15+/16 Engineer skill for App Router. Use when scaffolding production apps, enforcing RSC patterns, auditing codebases, or optimizing performance.
nextjs-production-debugger
Advanced debugging guide for Next.js App Router production issues including SSR/CSR bugs, hydration errors, runtime mismatches, performance, and caching.
nextjs-frontend-guidelines
Next.js 15 frontend development guidelines for YGS (영영사) React 19/TypeScript application. Modern patterns including App Router, Server/Client Components, shadcn/ui components, Tailwind CSS 4, multi-method authentication (Firebase/Kakao/JWT), admin dashboard patterns, and Korean localization. Use when creating components, pages, API routes, fetching data, styling, or working with frontend code.
nextjs-code-reviewer
code reviews. Use when Codex needs this specialist perspective or review style.
nextjs-best-practices
Next.js App Router principles. Server Components, data fetching, routing patterns.
nextjs-app-router-patterns
Master Next.js 14+ App Router with Server Components, streaming, parallel routes, and advanced data fetching. Use when building Next.js applications, implementing SSR/SSG, or optimizing React Serve...
newsletter-events-write
Generate markdown newsletters from stored events. Use when the user wants to create, write, or generate a newsletter from scraped events.