| name | bynder-connector-check |
| description | Audit Bynder Marketplace connector coverage — what's installed, what's actively used, what's stale, and which Tier 1 adoption-driver connectors are missing. Faster, narrower than bynder-optimization-audit — use when the question is specifically about connector fit, not full implementation health. Produces a recommendation list with effort and impact per item. |
| type | skill |
| project | skills-library |
| plugin | bynder |
| aliases | ["bynder-connector-check"] |
| tags | ["type/skill","plugin/bynder","topic/bynder","topic/marketplace","topic/connectors","scope/orchestrator"] |
| status | active |
Bynder connector check (orchestrator)
Use the bynder-marketplace-connectors skill to audit OOTB connector coverage on an existing Bynder deployment and recommend installs.
Faster, narrower than bynder-optimization-audit — run this when the user's question is specifically "are we using the right connectors?" or "what would drive adoption faster?" rather than a full implementation audit.
The flow:
- Inventory installed connectors — pull from Bynder portal admin (Settings → Integrations → Apps / Connectors).
- Pull connector usage from Analytics —
bynder-foundations.md references the Analytics API integration usage endpoint. Connectors with zero quarterly traffic are usually misconfigured or forgotten.
- Verify connector health for each installed:
- Latest release within last 12 months?
- Verified-by-Bynder badge present?
- Service-account auth still valid?
- Bynder-side configuration (return-derivative, default filters) still aligned with current editorial intent?
- Host-system field assignments still valid (content types haven't been retired)?
- Identify Tier 1 adoption-driver gaps — every deployment should have:
- Microsoft 365 (Word, PowerPoint, Outlook, Teams)
- Slack
- Adobe Creative Cloud (Photoshop, Illustrator, InDesign)
- Figma
These cost almost nothing to install and drive measurable adoption.
- Identify Tier 2 system gaps — confirm CMS / commerce / marketing-automation / PIM systems in use have OOTB connectors installed where supported.
- For systems without an OOTB connector, evaluate whether a custom UCV embed (
bynder-compact-view) is justified by editorial flow.
- For systems with an OOTB connector that doesn't quite fit, evaluate the layered pattern — install OOTB for baseline + custom UCV for gap-specific flows.
Produce a recommendation list with effort estimate (S/M/L) per item and expected adoption / integration impact.
Don't propose custom UCV before checking the Marketplace listing. Connectors evolve; what wasn't supported a year ago may be now.
Don't recommend installing every available connector — Tier 1 reflexively, Tier 2 when scope justifies, Tier 3 only on explicit fit.
