Bynder Marketplace OOTB connectors — when to install rather than build. Covers the connector catalog (Contentful, Adobe Creative Cloud, Salesforce, Sitecore, AEM, WordPress, Drupal, Microsoft 365, Slack, Hootsuite, Workfront, Akeneo, and more), the build-vs-buy decision, the install pattern (both-sides configuration)…
The audit-first remediation playbook for existing Bynder implementations that aren't delivering value. Covers an eight-metric health rubric (taxonomy, derivatives, permissions, integrations, adoption, analytics, brand-guidelines activation, governance), the diagnostic prompts that point to specific findings, the…
Permission profiles, asset-level security, and the Bynder Workflow module — designing who-can-see-edit-approve-publish-what, scoping access to brand / region / metaproperty values, the Workflow module's campaign/job/task structure, review and approval cycles, and scheduled publishing. Covers the practical permission…
Portal, sub-portal, account, and environment architecture for Bynder — when to use a single portal vs. multiple, how to split sub-portals for multi-brand, custom domains, dev/test/prod patterns where the plan supports separate environments, and the trade-offs between strong isolation and shared-asset-pool flexibility.…
Run a quarterly Bynder hygiene sweep — audit, then sequentially fix tag/derivative drift, permission decay, broken webhooks, stale brand-guideline pages, and connector misconfigurations. Orchestrator for Slalom-built deployments on a quarterly review cadence (catch drift before it compounds) — distinct from…
Bynder webhook configuration and asset-event handling — subscribing to asset.created/updated/deleted/archived and metaproperty events, HMAC signature verification, retry behavior, payload patterns (lookup-then-fetch since payloads are minimal), idempotent receivers, and the downstream-cache invalidation patterns that…
Claude tooling skills for Cowork and Claude Code. Two skills: claude-plugin-creator scaffolds new plugins (folder structure, manifest, .plugin build, Cowork install) with empirically-established validation rules; claude-orchestrator designs the orchestration layer for new Cowork projects (CLAUDE.md routing…
Plugin orchestrator. Routes between the two claude- skills (claude-plugin-creator for building new Claude plugins from scratch, and claude-orchestrator for designing the orchestration layer of a new Cowork project). Use this agent as the first call for any Claude-tooling task — plugin creation, hook design, MCP server…
Orchestration architect for Claude projects: Cowork project setup, Claude Code sessions, and plugin-internal coordination. Designs how multiple skills, agents, and commands work together for multi-step tasks. Use when starting a new Cowork project that coordinates multiple plugins, when a task spans multiple domains…
Plugin engineer for Cowork and Claude Code. Scaffolds new plugins from scratch: folder structure, plugin.json manifest, skills, agents, slash commands, and the .plugin build for Cowork's drag-and-drop installer. Use when starting a new plugin, cleaning up an existing one, building the distribution artifact…