@zaip-ai/cli 1.3.8 → 1.4.2

package/templates/.agents/skills/zaip-skill-meta-devtools-api-integration/references/upstream.md

@@ -0,0 +1,126 @@
+---
+name: api-integration
+description: "Guide a developer through setting up a Meta API integration from scratch — discovers the right APIs, fetches setup guides, authentication requirements, permissions, and code examples. Use when the user wants to build with a specific Meta product (WhatsApp, Instagram, Messenger, Pages, Ads, etc.)."
+allowed-tools: mcp__devtools__devtools_discovery, mcp__devtools__devtools_app, mcp__devtools__devtools_app_review, mcp__devtools__devtools_app_list, mcp__devtools__devtools_skill_invocation
+license: MIT
+---
+
+# API Integration
+
+Help a developer go from "I want to integrate with X" to having everything they need to start writing code.
+
+## Workflow
+
+1. **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.
+
+2. **Identify the integration.** Ask the user what they want to build if not clear. Common integrations:
+   - WhatsApp Business API (send/receive messages, templates, media)
+   - Instagram Graph API (publish content, read insights, manage comments)
+   - Messenger Platform (chatbots, send API, webhooks)
+   - Pages API (post content, read insights, manage pages)
+   - Marketing API (create campaigns, manage ads, read analytics)
+   - Login with Facebook / Login with Instagram
+   - Facebook Login for Business
+
+3. **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"
+   - e.g., "WhatsApp Business API getting started"
+
+   **Search 2 — Authentication and access tokens:**
+   - `devtools_discovery` → `search_docs` for authentication requirements
+   - e.g., "WhatsApp Business API access token authentication"
+
+   **Search 3 — Required permissions and app review:**
+   - `devtools_discovery` → `search_docs` for permissions
+   - e.g., "WhatsApp Business API permissions"
+   - Also check the app if an app_id is provided: `devtools_app_review` → `requirements` and `privileges`
+
+   **Search 4 — Core API endpoints:**
+   - `devtools_discovery` → `search_docs` for the specific operations the user needs
+   - e.g., "WhatsApp send message API" or "Instagram publish media API"
+
+   **Search 5 — Webhooks (if applicable):**
+   - `devtools_discovery` → `search_docs` for webhook setup
+   - e.g., "WhatsApp webhooks setup"
+
+   **Search 6 — Rate limits and quotas:**
+   - `devtools_discovery` → `search_docs` for product-specific rate limits and throughput tiers
+   - e.g., "WhatsApp Business API rate limits messaging tiers" or "Instagram API rate limits"
+
+   **Search 7 — Code examples and SDKs:**
+   - `devtools_discovery` → `search_docs` for SDK, client library, or code samples
+   - Try product-specific queries first: "WhatsApp Business Platform Node.js" or "Instagram Graph API Python"
+   - If no SDK results, search for "Graph API client library" or the product's quickstart guide
+   - Fall back to constructing examples from the endpoint documentation in Search 4
+
+   Run 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.
+
+4. **Check app readiness** (if the user has an app):
+   - If they referred to the app by **name** (or aren't sure of the ID), resolve it to an `app_id` first via `devtools_app_list` (action `list`); if ambiguous, show the candidates (name, ID, viewer role) and ask them to pick
+   - `devtools_app` → `basic_settings` to confirm app type and status
+   - `devtools_app_review` → `privileges` to see what's already approved
+   - `devtools_app_review` → `requirements` to see what's needed
+
+5. **Synthesize an integration guide.** Extract the key information from search results — do NOT dump raw results. Organize findings into an actionable document:
+
+   ### Guide Format
+
+   **Overview**
+   - What the API does and what the user can build with it
+   - Link to the official product documentation
+
+   **Prerequisites**
+   - Meta Developer account
+   - App type required (Business, Consumer, etc.)
+   - Any product-specific prerequisites (e.g., WhatsApp Business Account, Facebook Page)
+
+   **Authentication**
+   - Token type needed (User, Page, System User, etc.)
+   - How to generate tokens
+   - Token permissions/scopes required
+   - Token expiration and refresh flow
+
+   **Required Permissions**
+   - List each permission needed and what it grants
+   - Which permissions need App Review vs. are auto-approved
+   - If app_id provided: which are already granted vs. still needed
+
+   **Setup Steps**
+   - Step-by-step from zero to first API call
+   - Include webhook setup if the integration requires it
+
+   **Key API Endpoints**
+   - Each endpoint with: method, URL pattern, key parameters, example response
+   - Focused on what the user asked for, not an exhaustive list
+
+   **Code Example**
+   - A working starter example in the user's preferred language
+   - Include authentication, a basic API call, and error handling
+   - Use the official SDK if one exists, raw HTTP (curl/fetch) if not
+   - Include webhook handler code if the integration is webhook-based
+
+   **Rate Limits and Quotas**
+   - Product-specific rate limits and throughput tiers (e.g., WhatsApp messaging tiers: 1K/10K/100K/unlimited)
+   - Per-endpoint rate limits if applicable
+   - Suggest `/api-health` for ongoing monitoring
+
+   **Common Pitfalls**
+   - Product-specific gotchas the docs call out
+   - Permission mistakes, token type confusion, webhook verification issues
+
+6. **Offer next steps:**
+   - `/app-review-prep` if permissions need App Review
+   - `/webhook-setup` if the integration uses webhooks
+   - `/api-health` to monitor usage once live
+
+7. **End tracking.** After completing all preceding steps, call `devtools_skill_invocation` with action `end` and `skill_name` `api-integration`.
+
+## Tips
+
+- Always search multiple times with different queries. A single search rarely covers authentication + permissions + endpoints + examples.
+- Prefer the user's stated language/framework for code examples. Default to Node.js/JavaScript if not specified.
+- If the user has an app_id, cross-reference their current permissions against what the integration requires — this saves them time.
+- Some integrations (WhatsApp, Instagram) require a Business-type app. Call this out early if the user's app is the wrong type.
+- Webhook-based integrations (Messenger, WhatsApp) won't work without a callback URL. Suggest `/webhook-setup` proactively.

package/templates/.agents/skills/zaip-skill-meta-devtools-app-health-check/SKILL.md

@@ -0,0 +1,12 @@
+---
+name: zaip-skill-meta-devtools-app-health-check
+description: Use Meta Social Technologies Dev Tools to inspect an app's configuration, health signals, and actionable warnings.
+---
+
+# Meta Dev Tools: App Health Check
+
+Adapted from Meta's official `app-health-check` skill (MIT; `facebook/agentic-tools` commit `2a1a2710ae1907906adf441fcb8cdea4582f9065`). Resolve the app ID, read its health/configuration signals and present prioritized findings with source evidence. Do not infer a passing app from absent fields. Keep diagnostics read-only and require approval for app changes.
+
+Read the complete [official workflow snapshot](references/upstream.md) and apply `RULE-META-MCP` before tool use.
+
+Follow the [central Dev Tools setup](../zaip-skill-meta-devtools-search-docs/references/setup.md).

package/templates/.agents/skills/zaip-skill-meta-devtools-app-health-check/agents/openai.yaml

@@ -0,0 +1,4 @@
+interface:
+  display_name: "Meta Dev Tools App Health"
+  short_description: "Verifica sinais e configuração de app Meta"
+  default_prompt: "Use $zaip-skill-meta-devtools-app-health-check para verificar a saúde de um app Meta."

package/templates/.agents/skills/zaip-skill-meta-devtools-app-health-check/references/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) Meta Platforms, Inc. and affiliates.
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/templates/.agents/skills/zaip-skill-meta-devtools-app-health-check/references/upstream.md

@@ -0,0 +1,67 @@
+---
+name: app-health-check
+description: "Run a comprehensive health check on a Meta app — audits settings, security, compliance, app review status, rate limits, and API deprecations in one pass. Use when you want a full picture of an app's current state."
+allowed-tools: mcp__devtools__devtools_app, mcp__devtools__devtools_app_review, mcp__devtools__devtools_compliance, mcp__devtools__devtools_api_usage, mcp__devtools__devtools_app_list, mcp__devtools__devtools_skill_invocation
+license: MIT
+---
+
+# App Health Check
+
+Run a full audit of a Meta app and produce an actionable report.
+
+## Workflow
+
+1. **Start tracking.** Before any other work, call `devtools_skill_invocation` with action `start` and `skill_name` `app-health-check`. Pass `skill_name` `app-health-check` on every `devtools_*` tool call in the following steps.
+
+2. **Identify the app.** Ask the user for the app **name or ID**. If they give a name (or aren't sure of the ID), call `devtools_app_list` (action `list`) and resolve it to an `app_id` — match the name case-insensitively. If several apps match or it's ambiguous, show the candidates (name, ID, viewer role) and ask the user to pick. If they give a numeric ID, use it directly.
+
+3. **Collect data in parallel.** Run all calls concurrently to minimize latency:
+   - `devtools_app` with action `basic_settings` — app name, category, platform, contact info
+   - `devtools_app` with action `security` — app secret rotation, allowed domains, data deletion URL
+   - `devtools_compliance` with action `status` — open required actions, violations, recommendations
+   - `devtools_app_review` with action `status` — current review state, pending submissions
+   - `devtools_api_usage` with action `rate_limits` — current rate limit health
+   - `devtools_api_usage` with action `deprecations` — deprecated APIs needing migration
+
+4. **Synthesize the report.** Organize findings into these sections:
+
+   ### Report Format
+
+   **App Overview**
+   - App name, ID, category, status
+
+   **Security**
+   - Highlight any issues: missing data deletion URL, stale app secret, overly broad domain allowlist
+   - Flag if App Secret has not been rotated recently
+
+   **Compliance**
+   - List any open required actions with deadlines
+   - List any active violations
+   - Summarize recommendations
+
+   **App Review**
+   - Current review status
+   - Any pending or rejected submissions
+   - Permissions/features that still need review
+
+   **API Health**
+   - Rate limit status: report the `overall_status` field as returned — `healthy`, `warning`, `critical`, `throttled`, or `unmetered`
+   - Usage at or above the 70% warning band, flagging 90%+ as critical
+   - Deprecated APIs with severity and migration recommendations
+
+   **Action Items**
+   - Prioritized list of things to fix, ordered by severity (violations > required actions > recommendations > improvements)
+
+5. **Offer next steps.** Suggest relevant follow-up skills:
+   - `/compliance-check` for deeper compliance remediation
+   - `/app-review-prep` if there are pending review requirements
+   - `/webhook-setup` if webhooks aren't configured yet
+   - `/api-health` for deeper API usage analysis and endpoint-level investigation
+
+6. **End tracking.** After completing all preceding steps, call `devtools_skill_invocation` with action `end` and `skill_name` `app-health-check`.
+
+## Tips
+
+- If any MCP call fails, report the failure in the relevant section rather than aborting the whole check.
+- Always include the app ID in the report header for easy reference.
+- For apps with no issues, keep the report short — don't pad with unnecessary detail.

package/templates/.agents/skills/zaip-skill-meta-devtools-app-review-prep/SKILL.md

@@ -0,0 +1,12 @@
+---
+name: zaip-skill-meta-devtools-app-review-prep
+description: Use Meta Social Technologies Dev Tools to prepare a Meta app-review submission from documented permissions and evidence.
+---
+
+# Meta Dev Tools: App Review Prep
+
+Adapted from Meta's official `app-review-prep` skill (MIT; `facebook/agentic-tools` commit `2a1a2710ae1907906adf441fcb8cdea4582f9065`). Discover current requirements for each permission, inventory the app's actual use and list evidence gaps. Prepare a review checklist and draft explanations only. Submitting review material or modifying app settings remains an approval-gated external action.
+
+Read the complete [official workflow snapshot](references/upstream.md) and apply `RULE-META-MCP` before tool use.
+
+Follow the [central Dev Tools setup](../zaip-skill-meta-devtools-search-docs/references/setup.md).

package/templates/.agents/skills/zaip-skill-meta-devtools-app-review-prep/agents/openai.yaml

@@ -0,0 +1,4 @@
+interface:
+  display_name: "Meta App Review Prep"
+  short_description: "Prepara requisitos e evidências para app review"
+  default_prompt: "Use $zaip-skill-meta-devtools-app-review-prep para preparar o app review Meta."

package/templates/.agents/skills/zaip-skill-meta-devtools-app-review-prep/references/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) Meta Platforms, Inc. and affiliates.
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/templates/.agents/skills/zaip-skill-meta-devtools-app-review-prep/references/upstream.md

@@ -0,0 +1,69 @@
+---
+name: app-review-prep
+description: "Prepare a Meta app for App Review — checks current status, outstanding requirements, granted privileges, and submission history. Use before submitting an app for review."
+allowed-tools: mcp__devtools__devtools_app_review, mcp__devtools__devtools_app, mcp__devtools__devtools_compliance, mcp__devtools__devtools_app_list, mcp__devtools__devtools_skill_invocation
+license: MIT
+---
+
+# App Review Prep
+
+Check everything needed before submitting a Meta app for App Review.
+
+## Workflow
+
+1. **Start tracking.** Before any other work, call `devtools_skill_invocation` with action `start` and `skill_name` `app-review-prep`. Pass `skill_name` `app-review-prep` on every `devtools_*` tool call in the following steps.
+
+2. **Identify the app.** Ask the user for the app **name or ID**. If they give a name (or aren't sure of the ID), call `devtools_app_list` (action `list`) and resolve it to an `app_id` — match the name case-insensitively. If several apps match or it's ambiguous, show the candidates (name, ID, viewer role) and ask the user to pick. If they give a numeric ID, use it directly.
+
+3. **Collect review data in parallel.** Run all calls concurrently:
+   - `devtools_app` with action `basic_settings` — app name, category, status for report context
+   - `devtools_app_review` with action `status` — current review state
+   - `devtools_app_review` with action `requirements` — what's needed for approval
+   - `devtools_app_review` with action `privileges` — currently granted permissions/features
+   - `devtools_app_review` with action `history` — past submissions and their outcomes
+   - `devtools_compliance` with action `status` — compliance blockers that could prevent approval
+
+4. **Analyze readiness.** Evaluate:
+   - Are all required items complete?
+   - Are there compliance violations that would block review?
+   - Have previous submissions been rejected? If so, what was the reason?
+   - Which permissions/features are already approved vs. still needed?
+
+5. **Produce a readiness report:**
+
+   ### Report Format
+
+   **Current Status**
+   - Review state (e.g., not submitted, in review, approved, rejected)
+   - Last submission date and outcome (if any)
+
+   **Granted Privileges**
+   - List of approved permissions and features
+
+   **Outstanding Requirements**
+   - Each requirement with its completion status
+   - Clear description of what's needed to fulfill incomplete items
+
+   **Compliance Blockers**
+   - Any violations or required actions that must be resolved before submission
+
+   **Submission History**
+   - Past submissions with dates, statuses, and rejection reasons (if any)
+   - Pattern analysis if there are repeated rejections
+
+   **Readiness Verdict**
+   - READY: all requirements met, no blockers
+   - NOT READY: list exactly what needs to be done, in priority order
+
+6. **Suggest next steps** based on the verdict:
+   - If NOT READY: specific actions to take, in order
+   - If READY: guidance on what to expect during the review process
+   - If there are compliance issues: suggest `/compliance-check` for remediation
+
+7. **End tracking.** After completing all preceding steps, call `devtools_skill_invocation` with action `end` and `skill_name` `app-review-prep`.
+
+## Tips
+
+- Rejected submissions often cite the same issues. If history shows a pattern, call it out prominently.
+- Compliance status is a prerequisite — resolve violations before worrying about other requirements.
+- Some requirements need evidence (screenshots, privacy policy URLs, etc.) that can't be checked programmatically. Flag these as "manual verification needed."

package/templates/.agents/skills/zaip-skill-meta-devtools-compliance-check/SKILL.md

@@ -0,0 +1,12 @@
+---
+name: zaip-skill-meta-devtools-compliance-check
+description: Use Meta Social Technologies Dev Tools to inspect Meta app compliance status and document remediation needs.
+---
+
+# Meta Dev Tools: Compliance Check
+
+Adapted from Meta's official `compliance-check` skill (MIT; `facebook/agentic-tools` commit `2a1a2710ae1907906adf441fcb8cdea4582f9065`). Resolve the exact app and retrieve its compliance signals. Report status, deadlines, requested remediation and evidence gaps as observed. Do not certify compliance or submit remediation automatically.
+
+Read the complete [official workflow snapshot](references/upstream.md) and apply `RULE-META-MCP` before tool use.
+
+Follow the [central Dev Tools setup](../zaip-skill-meta-devtools-search-docs/references/setup.md).

package/templates/.agents/skills/zaip-skill-meta-devtools-compliance-check/agents/openai.yaml

@@ -0,0 +1,4 @@
+interface:
+  display_name: "Meta Compliance Check"
+  short_description: "Consulta status e pendências de compliance Meta"
+  default_prompt: "Use $zaip-skill-meta-devtools-compliance-check para verificar compliance de um app Meta."

package/templates/.agents/skills/zaip-skill-meta-devtools-compliance-check/references/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) Meta Platforms, Inc. and affiliates.
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/templates/.agents/skills/zaip-skill-meta-devtools-compliance-check/references/upstream.md

@@ -0,0 +1,79 @@
+---
+name: compliance-check
+description: "Check compliance status for a Meta app — surfaces open required actions, active violations, and recommendations with remediation guidance. Use to audit compliance posture or resolve compliance blockers."
+allowed-tools: mcp__devtools__devtools_compliance, mcp__devtools__devtools_app, mcp__devtools__devtools_app_list, mcp__devtools__devtools_skill_invocation
+license: MIT
+---
+
+# Compliance Check
+
+Audit the compliance posture of a Meta app and provide remediation guidance.
+
+## Workflow
+
+1. **Start tracking.** Before any other work, call `devtools_skill_invocation` with action `start` and `skill_name` `compliance-check`. Pass `skill_name` `compliance-check` on every `devtools_*` tool call in the following steps.
+
+2. **Identify the app.** Ask the user for the app **name or ID**. If they give a name (or aren't sure of the ID), call `devtools_app_list` (action `list`) and resolve it to an `app_id` — match the name case-insensitively. If several apps match or it's ambiguous, show the candidates (name, ID, viewer role) and ask the user to pick. If they give a numeric ID, use it directly.
+
+3. **Collect data in parallel:**
+   - `devtools_compliance` with action `status` — full compliance status
+   - `devtools_app` with action `basic_settings` — app context (name, category, status)
+   - `devtools_app` with action `data_protection_officer` — DPO contact info
+
+4. **Analyze compliance status.** Categorize findings by severity:
+
+   **Violations** (critical — may result in app restrictions or removal)
+   - What the violation is
+   - When it was flagged
+   - What action is required
+   - Deadline for resolution
+
+   **Required Actions** (high — must be completed by deadline)
+   - Description of the required action
+   - Deadline
+   - Steps to complete
+
+   **Recommendations** (low — suggested improvements)
+   - What's recommended and why
+   - How to implement
+
+5. **Produce the compliance report:**
+
+   ### Report Format
+
+   **App Overview**
+   - App name, ID, category
+
+   **Compliance Score**
+   - Overall status: COMPLIANT / ACTION REQUIRED / VIOLATION
+   - Count of items by severity
+
+   **Violations** (if any)
+   - Each violation with description, deadline, and remediation steps
+
+   **Required Actions** (if any)
+   - Each action with description, deadline, and steps to complete
+
+   **Recommendations** (if any)
+   - Each recommendation with description and implementation guidance
+
+   **Data Protection Officer**
+   - Current DPO contact info
+   - Flag if DPO info is missing or incomplete
+
+   **Action Plan**
+   - Prioritized list: violations first, then required actions by deadline, then recommendations
+   - For each item, provide specific steps the developer can take
+
+6. **Suggest follow-ups:**
+   - If violations exist: emphasize urgency and potential consequences
+   - If DPO info is missing: explain why it matters and how to set it up
+   - If app review is blocked by compliance: suggest `/app-review-prep` after resolving issues
+
+7. **End tracking.** After completing all preceding steps, call `devtools_skill_invocation` with action `end` and `skill_name` `compliance-check`.
+
+## Tips
+
+- Compliance deadlines are hard deadlines — missing them can result in app restrictions.
+- Some compliance items require changes in the Meta Developer Dashboard that can't be done via API. Flag these clearly as "manual action required in Developer Dashboard."
+- If the app is fully compliant, keep the report brief and congratulatory.

package/templates/.agents/skills/zaip-skill-meta-devtools-debug-access-token/SKILL.md

@@ -0,0 +1,14 @@
+---
+name: zaip-skill-meta-devtools-debug-access-token
+description: Diagnose Meta token metadata safely without accepting, storing, or exposing an access token or app secret.
+---
+
+# Meta Dev Tools: Debug Access Token
+
+Adapted from Meta's official `debug-access-token` skill (MIT; `facebook/agentic-tools` commit `2a1a2710ae1907906adf441fcb8cdea4582f9065`), excluding its bundled credential script. Never request a token or app secret in chat. The operator uses Meta's Access Token Debugger and shares only redacted metadata: validity, token type, app ID, expiry, scopes and error code/subcode. Interpret those values and recommend remediation; rotate a credential pasted into chat.
+
+Read the complete [official workflow snapshot](references/upstream.md) and apply `RULE-META-MCP` before tool use.
+
+Follow the [central Dev Tools setup](../zaip-skill-meta-devtools-search-docs/references/setup.md).
+
+Do not execute the unavailable upstream token-probe script; the snapshot is reference-only.

package/templates/.agents/skills/zaip-skill-meta-devtools-debug-access-token/agents/openai.yaml

@@ -0,0 +1,4 @@
+interface:
+  display_name: "Meta Token Debug"
+  short_description: "Diagnostica metadados de token sem expor segredos"
+  default_prompt: "Use $zaip-skill-meta-devtools-debug-access-token para diagnosticar um token Meta com dados redigidos."

package/templates/.agents/skills/zaip-skill-meta-devtools-debug-access-token/references/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) Meta Platforms, Inc. and affiliates.
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.