القائمة
Make arbitrary authenticated HTTP calls to configured Analytics provider APIs when first-class actions are too narrow.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
How to look up version-matched Agent Native framework docs in node_modules. Use before coding against @agent-native/core APIs or advanced features.
Use Content for repo-backed Markdown/MDX docs, blogs, resources, rich document editing, local components, shareable copies, and Content local-file workspaces. Prefer Content actions over raw filesystem writes when available.
All AI features in Clips — titles, summaries, chapters, tags, filler-word removal — delegate to the agent chat via sendToAgentChat except the narrow media pipeline path: transcription. Use when adding any AI-powered feature.
How Clips shares recordings — composes with the framework sharing skill and adds password, expiry, embed URLs, and view-counting. Use when wiring the share dialog, building embed links, adding a password, or debugging who can see a recording.
Cross-platform pattern for handling messaging integration webhooks (Slack, Telegram, WhatsApp, email, etc.) on serverless hosts. Use when adding a new integration adapter, debugging dropped messages, or wiring long-running agent work into a webhook handler.
Turn ordinary text plans into rich interactive visual plans with diagrams, file maps, annotated code, open questions, and UI/prototype review when useful.
| name | provider-api |
| description | Make arbitrary authenticated HTTP calls to configured Analytics provider APIs when first-class actions are too narrow. |
Use provider-specific actions for common jobs, but treat them as shortcuts, not limits. When a first-class action cannot express the endpoint, filters, request body, pagination mode, or API version needed, use:
provider-api-catalog to inspect provider base URL, auth style, docs/spec
URLs, placeholders, examples, and reusable corpusRecipes.provider-api-docs to fetch registered provider docs/spec URLs.provider-api-request to make the exact HTTP call. Credentials are injected
server-side, private/internal URLs are blocked, and secrets are redacted.Examples:
pnpm action provider-api-catalog --provider=hubspot
pnpm action provider-api-request --provider=hubspot --method=POST --path=/crm/v3/objects/deals/search --body='{"filterGroups":[{"filters":[{"propertyName":"products","operator":"CONTAINS_TOKEN","value":"Publish"}]}],"properties":["dealname","products","dealstage","closedate"],"limit":100}'
pnpm action provider-api-request --provider=bigquery --method=GET --path=/projects/{projectId}/datasets
Always cite provider, method, path, status, filters, row/sample count, and pagination/coverage gaps in analytical answers.
For source-record body searches across transcripts, messages, tickets, issues, notes, documents, or conversation logs, use the raw body endpoint or native provider search endpoint for that record type. Parent/container metadata such as call lists, titles, summaries, or briefs is discovery evidence only; it cannot support a "no mentions" or complete body-text claim.
Example corpus recipe:
pnpm action provider-corpus-job --operation=start --mode=batch-search --request='{"provider":"gong","method":"POST","path":"/calls/transcript","body":{"filter":{"callIds":[]}}}' --batch='{"inputDatasetId":"<staged-call-id-dataset>","inputValuePath":"id","batchSize":20,"itemBodyPath":"filter.callIds","responseItemsPath":"callTranscripts"}' --search='{"queries":["Figma MCP","model context protocol"],"textPaths":["transcript"],"idPaths":["callId"]}'