validate-profile
Validate a brand profile end-to-end — required fields, voice/audience completeness, connector reachability, credentials health, and compliance prerequisites — without exposing credential values. Run after any credential change or brand-profile edit.
npx skills add indranilbanerjee/digital-marketing-pro --skill validate-profile --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# /digital-marketing-pro:validate-profile — Brand Profile + Credential Health Check This skill is the canonical "is this brand ready to ship work?" gate. It validates a brand profile is complete enough for production use AND that every credential/connector referenced by the profile is actually reachable — **without ever printing credential values**. Use this skill: - After **`/digital-marketing-pro:brand-setup`** (or `/digital-marketing-pro:client-onboarding`) to confirm the new profile is production-ready. - After **rotating any API key** (Slack, HubSpot, Stripe, Ahrefs, GA4 service account, etc.) so connectivity is re-confirmed without exposing the new value in logs. - After **importing brand guidelines** (`/digital-marketing-pro:import-guidelines`) to confirm the merge succeeded. - As the **prerequisite check** before `/digital-marketing-pro:engagement`, `/digital-marketing-pro:campaign-plan`, or `/digital-marketing-pro:launch-campaign`. ## Why this skill exists For agencies running 50–200 client brands, brand profiles and credentials drift constantly: a junior changes a Slack channel, an API key rotates, a brand voice gets edited. The cost of running a 60-minute engagement on a
- Why this skill exists
- Validation dimensions
- Process
- Step 0 — Resolve the brand to validate
- Step 1 — Load the brand profile
- Step 2 — Required-field checks
- Step 3 — Compliance-jurisdiction cross-check
- Step 4 — Connector reachability (credential-safe)
- Step 5 — Output-path writeability
- Step 6 — Model-curator currency
- Step 7 — Report
- Behaviour rules
- Arguments
- Related skills + commands
test -d "$BRAND_DIR" || { echo "Brand directory not found at $BRAND_DIR — run /digital-marketing-pro:brand-setup first."; exit 1; }
test -f "$PROFILE" || { echo "profile.json missing under $BRAND_DIR — run /digital-marketing-pro:brand-setup."; exit 1; }
python "${CLAUDE_PLUGIN_ROOT}/scripts/connector-status.py" \
for url in $(jq -r '.mcpServers[] | select(.type=="http") | .url' .mcp.json); do
echo "$url -> HTTP $code"
done
test -w "$HOME/.claude-marketing/brands/{brand}/" || echo "BLOCK: brand directory is not writeable"
User-visible publish dir (dual-copy pattern)
if [ -n "$DIGITAL_MARKETING_PRO_PUBLISH_DIR" ]; then
test -w "$DIGITAL_MARKETING_PRO_PUBLISH_DIR" || echo "WARN: DIGITAL_MARKETING_PRO_PUBLISH_DIR ($DIGITAL_MARKETING_PRO_PUBLISH_DIR) is not writeable"What does the validate-profile skill do?
Validate a brand profile end-to-end — required fields, voice/audience completeness, connector reachability, credentials health, and compliance prerequisites — without exposing credential values. Run after any credential change or brand-profile edit.
How do I install it?
Run `npx skills add indranilbanerjee/digital-marketing-pro --skill validate-profile --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From indranilbanerjee/digital-marketing-pro, a repository with 700 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.