Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Meta Instagram Integration Readiness Audit

    1

    Find OAuth, webhook and App Review preparation gaps. Get a dated blocker map, reviewer walkthrough plan and separate technical and provider gates.

    $9

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Meta Instagram Integration Readiness Audit

    Meta Instagram Integration Readiness Audit

    Example session with this skill installed

    FICTIONAL supplied-evidence exercise; no live actions.

    Audit only. App uses Instagram Login; version not supplied. Role tester connects. Dashboard says Ready for testing, reviewer instructions 100%; business verification pending. Callback configured at preview.example.invalid but deployed app is app.example.invalid. Webhook challenge succeeds; no signed-event test. Screencast starts after login and reviewer credentials have not been tried. Official documentation unavailable in this exercise. Are we ready for external clients? Give blocker order and reviewer plan.

    • Read your context and instructions
    • Compiled the meta instagram integration

    Instagram integration readiness: meta-1

    Audit date: 2026-10-26. Fictional supplied-evidence audit only. No browser, network, provider calls, settings changes or credentials accessed.

    Evidence M1: Instagram Login; API version absent; a role tester connects. M2: dashboard Ready for testing and reviewer instructions 100%; business verification pending. M3: configured callback host preview.example.invalid differs from deployed app host app.example.invalid. M4: webhook challenge succeeds, no signed-event test. M5: screencast starts after login and reviewer credentials have not been tried. Official documentation is unavailable in this exercise. These example hosts are evidence labels, not verified reachable URLs.

    Technical readiness: partial/blocked for external-client acceptance. The callback/deployment discrepancy must be resolved or explained and tested; it does not identify a proven OAuth failure stage. Submission readiness: incomplete. Provider approval/external access: unverified; dashboard indicators and role tester success are insufficient. We cannot conclude the integration is ready for external clients.

    Action or gatePath-specific requirementEvidenceStatusOwner and next check
    Identify integrationInstagram Login, exact API version, app type/use case, professional account eligibility, app mode and target actorsM1 only establishes Login path and role testerUnknown beyond supplied pathIntegration owner: provide redacted path/version, account and mode/access evidence.
    Connect a role testerApplicable actor/role acceptance and OAuth completionM1 tester connectsSupported for that actor onlyQA: retain scoped evidence; do not extrapolate to external actors.
    Connect an external non-role clientExact endpoint/capability, permissions, access levels and account eligibility must match verified current path/version documentationNo external actor evidence, exact action scope or official docsUnknownOwner: supply product actions and official requirements before naming permissions.
    Callback routingExact authorization redirect, configured URI and deployed callback must be coherent and reachableM3 host discrepancyBlocked pending resolution/verificationEngineering: compare redacted full paths/schemes and deployment routing; propose alignment or explain intentional routing, then test when authorized.
    Business/access/review gatesApplicable business verification and permission approval require path-specific verificationM2 pending business verification; badges do not establish approvalUnknown eligibility; pending verification is openApp owner: verify applicability and actual permission/access decisions.
    Webhook challengeChallenge succeeds at the tested endpointM4Supported for challenge onlyEngineering: identify endpoint/environment.
    Authentic events and downstream effectsApplicable subscription, authenticity/signature checks, acknowledgement and processingNo signed-event evidenceUnknownEngineering/QA: authorized isolated event acceptance plan.
    Reviewer walkthroughAccessible reviewer actor, stable URLs, full login and visible permission-linked actionsM5 untried credentials, login omittedBlocked/incompleteReview owner: private provisioning, authorized rehearsal and replacement screencast.
    Token/storage/revocation/deletionPath-specific lifecycle and actual documented data practicesNo evidenceUnknownEngineering/privacy owner: supply redacted lifecycle and actual retention/deletion behavior.

    No exact permission or endpoint can responsibly be filled in: product actions and version-specific official requirements are missing. Instagram Login is the relevant path; do not import Facebook Login permissions or require a Facebook Page by assumption.

    Blocking dependency order

    1. Integration owner establishes exact path/version, intended product actions, actors, account type, app mode and applicable official requirements. Official-doc verification remains open; this audit cannot supply it.
    2. Engineering resolves or explains the callback/deployed-app discrepancy and verifies complete OAuth in the intended environment. Prior tester success may belong to another environment and does not settle the discrepancy.
    3. Review owner privately provisions and actually rehearses the reviewer actor through the reachable login path. Untested credentials block a credible walkthrough; no credentials belong in this report.
    4. Engineering/QA proves each requested action and relevant signed-event/downstream path, including token lifecycle and revocation/deletion. Produce the full screencast after this works.
    5. App owner confirms separate business-verification, mode/access and permission-review gates for external users. Resolve applicable pending gates and capture provider decisions. This can progress alongside engineering; local success cannot replace it.
    6. An explicitly authorized non-role test actor completes external-client acceptance once eligibility/access permits it. Record evidence before declaring readiness.

    Reviewer walkthrough

    Proposed, not executed: the owner supplies a stable full app starting URL and privately provisions the reviewer account through the provider-designated process. The supplied app.example.invalid host is not proof of a working URL.

    1. Start signed out at that URL; show the integration screen and click its actual connect control. Its label is not supplied and must be recorded from the UI.
    2. Capture the full Instagram Login redirect and consent flow for the reviewer actor. Show permissions corresponding to the requested product scope, without secrets.
    3. Return through the intended callback and show the connected account. Retain redacted state/code-stage evidence without exposing codes or tokens.
    4. For each needed permission, record actual product screen, exact clicks, API capability and expected/observed visible result. The owner must supply the feature actions before this exact script can be completed. Use test actors; real messaging/provider side effects need separate authorization.
    5. If webhooks are relevant, show an authorized isolated signed event received, acknowledged and reflected downstream; separately test invalid authenticity, retries and duplicates with a bounded plan.
    6. Show persisted connection after reload where supported and actual disconnect/revoke/delete behavior, with expected outcomes grounded in the product contract and official path-specific docs.

    Replace the partial screencast with end-to-end coverage including login. Independently rehearse private reviewer access before submission. Test-actor success still does not prove non-role eligibility.

    Data-handling questions for owner

    Supply actual data categories/purposes, storage boundaries, processors, retention, credential protection and revoke/delete behavior, plus matching published policies. Identify the operational and reviewer-support owners; do not invent compliance answers.

    Proposed acceptance versus observed results

    Observed only from supplied text: tester connection, dashboard indicators, pending verification, host discrepancy, challenge success, missing signed test and incomplete reviewer evidence. Full OAuth trace, official-doc verification, reviewer/browser rehearsal, signed-event processing, non-role acceptance and provider approval remain unverified.

    Next acceptance step: integration/app owner supplies redacted path/version and callback evidence; engineering resolves the routing question, then arranges an authorized reviewer login rehearsal. Submission, settings edits, real messages and production acceptance require separate authorization. No approval outcome or date is promised.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Map the actual Instagram Login/API path and version to product actions, minimal access and reviewer evidence. Review callback stages, role-versus-external actor access, webhook proof and data-handling gaps. Includes a readiness method, report template and fictional worked example. Independent preparation workflow; no affiliation with Meta and no approval guarantee. It does not add permissions, change provider settings, handle credentials or submit App Review. Current path-specific official requirements must be verified when tools are available; unavailable documentation remains an explicit gap. Fictional supplied-evidence exercises are documented separately; no live provider, database, browser or cross-agent compatibility acceptance is claimed.

    Cannot guarantee Meta approval or diagnose an exact permission from a generic error; official requirements and live acceptance need current verification.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 22 days ago

    Permissions

    Read Files

    Read bundled and supplied redacted evidence only. Optional browsing, saving a report, implementation and external effects depend on host tools and task authorization. No provider account or credentials required for supplied-evidence review.

    Listed22 days ago

    What's inside

    Frequently Asked Questions

    Four Markdown files: SKILL.md, one method reference, one report template and a fictional worked example. The listing icon is a separate asset.

    No production connector, credentials or runtime are bundled. Supplied-evidence analysis works from authorized redacted material; live checks depend on separately authorized host tools.

    No. The default deliverable is an evidence-linked analysis and proposed next steps. Implementation, settings changes, messaging and deployment require the task authorization.

    Two fictional supplied-evidence forward exercises for this skill using Codex, plus frontmatter, linked-resource and ZIP round-trip checks. No live integration or other-agent compatibility validation is claimed.

    Cannot guarantee Meta approval or diagnose an exact permission from a generic error; official requirements and live acceptance need current verification.

    Provide the task scope and the smallest authorized redacted source, configuration, usage or policy evidence relevant to the requested analysis. Missing evidence remains explicitly unknown; credentials and production customer exports are not required.

    New in APIs & Backend