Terminal
Terminal/Skill
Walks a developer through setting up a Meta API integration from scratch, covering authentication, permissions, endpoints and code examples.
By Meta
Works with
npx skills add facebook/agentic-tools --skill api-integrationHelp a developer go from "I want to integrate with X" to having everything they need to start writing code.
Start tracking. Before any other work, call devtools_skill_invocation with action start and skill_name api-integration. Pass skill_name api-integration on every devtools_* tool call in the following steps.
Identify the integration. Ask the user what they want to build if not clear. Common integrations:
Research the integration. Run multiple searches to build a complete picture. Do NOT stop at one search — layer queries to cover all aspects:
Search 1 — Overview and getting started:
devtools_discovery → search_docs with the product name + "getting started" or "overview"Search 2 — Authentication and access tokens:
devtools_discovery → search_docs for authentication requirementsSearch 3 — Required permissions and app review:
devtools_discovery → search_docs for permissionsdevtools_app_review → requirements and privilegesSearch 4 — Core API endpoints:
devtools_discovery → search_docs for the specific operations the user needsSearch 5 — Webhooks (if applicable):
devtools_discovery → search_docs for webhook setupSearch 6 — Rate limits and quotas:
devtools_discovery → search_docs for product-specific rate limits and throughput tiersSearch 7 — Code examples and SDKs:
devtools_discovery → search_docs for SDK, client library, or code samplesRun searches 1-5 in parallel for speed. Run 6-7 after if needed. Use max_results of 10 and pagination via offset to get comprehensive results. Refine queries if initial results are too broad or miss key topics.
Check app readiness (if the user has an app):
app_id first via devtools_app_list (action list); if ambiguous, show the candidates (name, ID, viewer role) and ask them to pickdevtools_app → basic_settings to confirm app type and statusdevtools_app_review → privileges to see what's already approveddevtools_app_review → requirements to see what's neededSynthesize an integration guide. Extract the key information from search results — do NOT dump raw results. Organize findings into an actionable document:
Overview
Prerequisites
Authentication
Required Permissions
Setup Steps
Key API Endpoints
Code Example
Rate Limits and Quotas
/api-health for ongoing monitoringCommon Pitfalls
Offer next steps:
/app-review-prep if permissions need App Review/webhook-setup if the integration uses webhooks/api-health to monitor usage once liveEnd tracking. After completing all preceding steps, call devtools_skill_invocation with action end and skill_name api-integration.
/webhook-setup proactively.