Run any Skill in Manus with one click

bynder-connector-check

Stars2

Forks2

UpdatedMay 19, 2026 at 01:17

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.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

bpainter

bpainter/composable-dxp-claude-marketplace

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

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.

More from this repository

same repository

video-factory-concept

bpainter/composable-dxp-claude-marketplace

Brainstorm distinct video concepts for a brief — cinematic videos, brand films, motion accents, and background loops for product websites. Produces 3–5 genuinely different creative directions (not five flavors of one safe idea), each with a premise, the feeling it creates, why it fits the product and placement, and how hard it is to pull off in Higgsfield. Use this skill any time the work starts with "what could this video be" — concepting a hero background loop, a launch film, a section divider, an explainer, or a social spot — even when the user just says "I need a video for X." First stage of the Video Factory chain; hands the chosen concept to video-factory-storyboard. Pulls toward concrete subjects over the drone-over-city / glowing-AI clichés that AI video defaults to.

2026-06-162

video-factory-create-flow

bpainter/composable-dxp-claude-marketplace

The main orchestrator for the Slalom Video Factory. Walks a user from "I need a video" to a ready-to-generate prompt package (and, on request, generated clips) via the Frame → Concept → Storyboard → Direct → Generate → Ship pipeline. Diagnoses intent, sequences the craft skills, and pauses for review at each handoff. Use this skill whenever someone wants a cinematic video, a brand film, a motion accent, or a background loop for a product website and hasn't already scoped it down to a single stage — "make me a hero video for X," "I need a background loop," "let's storyboard a launch film." For a single stage, route straight to that craft skill instead.

2026-06-162

video-factory-creative-direction

bpainter/composable-dxp-claude-marketplace

The motion taste layer for a video — lock one coherent look across every shot before any generation happens. Owns register, pacing, camera language, color and grade, light, grain/texture, and brand fit, so a multi-shot piece reads as one director shot it rather than a pile of clips. The motion analog of design-imagery. Use this skill any time a video needs art direction: setting the visual system for a brand film, keeping a background loop on-brand, grading decisions, or course- correcting clips that came back looking like different videos. Third stage of the Video Factory chain; reads a storyboard, writes a direction spec that video-factory-higgsfield-prompt turns into model parameters and prompt language. Actively rejects the drone-city / glowing-AI motion clichés.

2026-06-162

video-factory-higgsfield-prompt

bpainter/composable-dxp-claude-marketplace

Turn a directed storyboard into a ready-to-run Higgsfield prompt package and (when asked) execute the generations via the Higgsfield MCP. Owns model routing (seedance 2.0 / kling 3.0 default for video; nano banana pro / chatgpt image 2 for keyframes), the image-to-video prompt structure (motion, camera, atmosphere, sound over a start frame), parameter selection (resolution, duration, aspect, sound on/off, genre, end-frame for loops), negatives, retries, and web encoding handoff. Use this skill any time the task is "write the Higgsfield prompt," "generate this in Higgsfield," "what model and settings," "make the background loop," or turning shots into clips. Final craft stage of the Video Factory chain; reads concept + storyboard + direction and produces 40_Prompts.md plus generated keyframes and clips. Keyframe-first, loop- seam-aware, credit-disciplined.

2026-06-162

video-factory-storyboard

bpainter/composable-dxp-claude-marketplace

Turn a chosen video concept into a shot-by-shot storyboard ready to generate in Higgsfield — shot list with timing, camera move, framing, transition, and a keyframe-still prompt for every shot (because Higgsfield video models are image-to-video and animate a start frame). Use this skill any time a video idea needs to become an executable shot plan: storyboarding a hero background loop, a brand film, an explainer, a section divider, or a social spot — even when the user says "break this into shots," "plan the shots," or "what's the shot list." Second stage of the Video Factory chain; reads a concept (or a one-line idea) and hands a storyboard to video-factory-creative-direction and video-factory-higgsfield-prompt. Designs loop seams for background video and protects headline safe-areas.

2026-06-162

brand-naming

bpainter/composable-dxp-claude-marketplace

Senior naming expertise. Brainstorms brand names in three categories — literal, abstract, alliterative — with 15+ per category by default. Validates each candidate against existing brand collisions and industry-specific negative connotations (e.g., "Forge" for a law firm reads as "forged documents"). Screens for trademark and domain availability. Use when brainstorming, evaluating, or recommending names for products, companies, features, or offerings.

2026-06-032

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.

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.