validate-profile
Skill0 starsChanged 9 months agoMITView on GitHub
Read-only health check that a brand profile is production-ready: required fields, voice and audience completeness, guardrails, compliance-jurisdiction coverage, connector configuration and MCP reachability, output-path writeability, and model-registry age — reported per check as BLOCKER or WARNING without ever printing credential values. Triggers on \"/digital-marketing-pro:validate-profile\", \"is the brand setup correct\", \"check connector credentials\", \"profile sanity check\", \"we rotated an API key — is it wired up\". Reads profile.json and probes connectors via connector-status.py; the prerequisite gate before /digital-marketing-pro:engagement, /digital-marketing-pro:campaign-plan, and /digital-marketing-pro:launch-campaign.
- Reads credentials
2 other projects use a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- tlennon-ie/neurodocktheir own version, first seen Jun 18, 2026
- indranilbanerjee/digital-marketing-proedited, first seen Feb 12, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 1
- indranilbanerjee/digital-marketing-pro★ 93492% same
Wrote their own version · 1
- tlennon-ie/neurodock★ 14same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository163 other files it gives its agents.
- AGENTS.mdAGENTS.md
- ab-test-planSkill
- ad-creativeSkill
- add-integrationSkill
- aeo-auditSkill
- aeo-geoSkill
- agency-dashboardSkill
- analytics-insightsSkill
- anomaly-scanSkill
- attribution-modelSkill
- attribution-reportSkill
- audience-intelligenceSkill
- audience-profileSkill
- autopilot-statusSkill
- backlink-gapSkill
- brand-setupSkill
- budget-optimizerSkill
- budget-trackerSkill
- c2pa-metadataSkill
- campaign-auditSkill
- campaign-orchestratorSkill
- campaign-planSkill
- campaign-statusSkill
- case-study-planSkill
- checkSkill
- churn-riskSkill
- client-onboardingSkill
- client-proposalSkill
- client-reportSkill
- client-validation-documentSkill
- cohort-analysisSkill
- competitor-alertsSkill
- competitor-analysisSkill
- competitor-monitorSkill
- competitor-pagesSkill
- connectSkill
- content-briefSkill
- content-calendarSkill
- content-decay-scanSkill
- content-engineSkill
- content-repurposeSkill
- context-engineSkill
- continuous-improvement-loopSkill
- counter-narrativeSkill
- cowork-setupSkill
- creative-healthSkill
- creative-testing-frameworkSkill
- credential-switchSkill
- crisis-responseSkill
- crm-syncSkill
- croSkill
- dark-funnelSkill
- data-exportSkill
- data-importSkill
- digital-prSkill
- email-sequenceSkill
- emerging-channelsSkill
- engagement-workflowSkill
- entity-auditSkill
- eval-configSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 4 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 21
After /digital-marketing-pro:brand-setup (or /digital-marketing-pro:client-onboarding) to confirm the new profile is production-ready.
- Distinctive: line 22
After rotating any API key (Slack, HubSpot, Stripe, Ahrefs, GA4 service account, etc.) so connectivity is re-confirmed without exposing the …
- Very specific: line 23
After importing brand guidelines (/digital-marketing-pro:import-guidelines) to confirm the merge succeeded.
- Very specific: line 53
If --brand <slug> was passed, use it.
- Distinctive: line 119
If the registry is more than 90 days old, WARN:
- Distinctive: line 164
Read-only: Never modify the brand profile, credentials, MCP config, or any persistent state.
- Distinctive: line 165
Don't short-circuit: Run every check even after the first BLOCKER — agencies want the full punch list in one pass.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
/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 broken profile is hours of rework. This skill catches those drift cases in under 60 seconds.
The skill is read-only — it inspects state, never modifies it. It also never prints credential values — connector checks emit pass / fail / error-class without echoing the secret.
Validation dimensions
| Dimension | What's checked | Severity |
| Required identity | brand_name, industry, and a market/jurisdiction list non-empty — accept target_markets (what brand-setup actually writes) or target_jurisdictions (legacy). Checking only the legacy name made every freshly created brand fail its own validator on a BLOCKER | BLOCKER |
| Voice profile | tone, formality and energy populated under brand_voice (what brand-setup writes, and what content-engine and brand-voice-scorer.py both read) or under voice (legacy). The generator is the source of truth here — two consumers already follow it, so this validator was the outlier | BLOCKER for content work |
| Audience profile | target_audience.primary_persona with role + reading_level | WARNING |
| Guardrails | guardrails.prohibited_terms + guardrails.prohibited_claims non-empty. brand-setup does not create this block, so report it as a WARNING with the exact command to add it for an unregulated brand, and reserve BLOCKER for regulated industries — where a missing guardrail is a real risk, not a setup gap | BLOCKER for regulated industries (pharma, BFSI, healthcare, legal); WARNING otherwise |
| Compliance jurisdictions | Each declared jurisdiction has a matching rules entry in skills/context-engine/compliance-rules.md | BLOCKER |
| Connector config present | Every connector named in tracking.backend, integrations.*, analytics.* has its env vars / .mcp.json entry present (local check; live reachability comes from the MCP/curl probe below) | BLOCKER per unconfigured connector |
| MCP server health | Every entry in .mcp.json (if present) responds to a tools/list ping | WARNING |
| Credential storage | ~/.claude-marketing/brands/{brand}/credentials.json (or env vars) present for every backend referenced | BLOCKER |
| Output paths writeable | ~/.claude-marketing/brands/{brand}/ is writeable; the user-visible publish dir ($DIGITAL_MARKETING_PRO_PUBLISH_DIR or ~/Documents/DigitalMarketingPro/) is writeable | BLOCKER |
| Model curator currency | scripts/resolve_model.py --registry-age returns < 90 days | WARNING |
A BLOCKER means "do not let the user run engagement / campaign-plan / launch-campaign until this is fixed." A WARNING is surfaced but does not gate.
Process
Step 0 — Resolve the brand to validate
If --brand <slug> was passed, use it. Otherwise read the active brand from ~/.claude-marketing/brands/_active-brand.json (set by /digital-marketing-pro:switch-brand). If neither is available, error: "--brand <slug> required, or run /digital-marketing-pro:switch-brand first." Do NOT validate "everything" — validation is per-brand by design.
Step 1 — Load the brand profile
BRAND_DIR="$HOME/.claude-marketing/brands/{brand}"
test -d "$BRAND_DIR" || { echo "Brand directory not found at $BRAND_DIR — run /digital-marketing-pro:brand-setup first."; exit 1; }
PROFILE="$BRAND_DIR/profile.json"
test -f "$PROFILE" || { echo "profile.json missing under $BRAND_DIR — run /digital-marketing-pro:brand-setup."; exit 1; }Parse the profile JSON and capture: brand_name, industry, target_jurisdictions, voice.*, target_audience.*, guardrails.*, tracking.backend, integrations.*, analytics.*.
Step 2 — Required-field checks
Walk the checklist in the Validation dimensions table above. For each field, record one of: OK / WARN: <reason> / BLOCK: <reason>. Do NOT short-circuit — collect every issue so the user sees the full picture in one pass.
For regulated industries (industry matches any of pharma, pharmaceuticals, bfsi, banking, insurance, healthcare, legal, medical-devices), upgrade guardrails issues from WARNING to BLOCKER.
Step 3 — Compliance-jurisdiction cross-check
For every entry in target_jurisdictions, confirm skills/context-engine/compliance-rules.md contains a matching section header (e.g. ### 1.11 India — DPDPA). If a jurisdiction is declared but not covered, BLOCK with: "Jurisdiction {X} declared in profile but no compliance rules for it — engagement will produce non-compliant deliverables."
Step 4 — Connector reachability (credential-safe)
For each backend referenced in tracking.backend, integrations.crm, integrations.email, integrations.cms, integrations.analytics, integrations.social, run the matching health probe via scripts/connector-status.py:
python "${CLAUDE_PLUGIN_ROOT}/scripts/connector-status.py" \
--action status \
--brand "{brand}" \
--connectors "{comma-separated list inferred from profile}" \
--probe-only --no-secretsconnector-status.py --probe-only runs a local readiness check: it verifies that the required environment variables / .mcp.json entry for each connector are present and non-empty. It does NOT open a live network connection or make a whoami call — so it reports a config-level class (CONFIGURED / MISSING_ENV / NOT_IN_MCP), not a live HTTP status. --no-secrets guarantees it never echoes, logs, or writes a credential value. For an actual liveness check, use the connector's MCP tools/list endpoint or the HTTP curl probe below.
For MCP servers in .mcp.json (if present at the brand or project level), run a tools/list ping against each via mcp__connector__* if the connector is loaded, or invoke a 5-second curl HEAD against the configured url for HTTP MCPs:
for url in $(jq -r '.mcpServers[] | select(.type=="http") | .url' .mcp.json); do
code=$(curl -sS -o /dev/null -w "%{http_code}" -m 5 "$url" || echo "000")
echo "$url -> HTTP $code"
doneHTTP 200, 204, 401 (auth required for GET — POST will work), and 405 (method not allowed for GET — POST will work) all count as "reachable". 404, 000 (DNS / timeout), 5xx count as BLOCK.
Step 5 — Output-path writeability
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"
elif [ -d "$HOME/Documents" ]; then
test -w "$HOME/Documents" || echo "WARN: ~/Documents is not writeable — the user-visible publish copy will fail"
fiStep 6 — Model-curator currency
python "${CLAUDE_PLUGIN_ROOT}/scripts/resolve_model.py" --registry-ageIf the registry is more than 90 days old, WARN: "model_registry.json is {N} days old — frontier models change every ~6 weeks. Run scripts/refresh_models.py to check drift." (Do not block — the curator auto-falls-forward on deprecated ids, so an older registry is degraded, not broken.)
Step 7 — Report
Print a structured report. ALWAYS show every check (don't only print failures — agencies need positive confirmation for the rest):
🔎 Brand profile validation — {brand_name}
Slug: {brand} · Industry: {industry} · Jurisdictions: {list}
✅ Required identity brand_name, industry, target_jurisdictions all set
✅ Voice profile tone={tone} · formality={formality} · energy={energy}
⚠️ Audience profile primary_persona.role set, reading_level MISSING
✅ Guardrails {N} prohibited_terms, {M} prohibited_claims (industry={industry})
✅ Compliance jurisdictions EU-GDPR ✓ · IN-DPDPA ✓ · US-CCPA ✓
🛑 Connector — Slack MISSING_ENV (SLACK_* env not set — add via /digital-marketing-pro:add-integration slack)
✅ Connector — HubSpot OK (workspace acme-corp, 1247 contacts)
✅ Connector — Stripe OK
✅ MCP — gmailmcp.googleapis.com HTTP 405 (alive)
✅ Output paths ~/.claude-marketing/brands/{brand}/ writeable; ~/Documents/DigitalMarketingPro/ writeable
⚠️ Model curator registry is 102 days old — consider scripts/refresh_models.py
Decision: 🛑 BLOCKED — Slack connector not configured. Fix before running:
• /digital-marketing-pro:engagement
• /digital-marketing-pro:campaign-plan
• /digital-marketing-pro:launch-campaign
Re-run /digital-marketing-pro:validate-profile after fixing.Also emit a machine-readable JSON summary so it can be consumed by /digital-marketing-pro:check, /digital-marketing-pro:status, or downstream automation:
{
"brand": "{slug}",
"decision": "blocked | passed | passed_with_warnings",
"blockers": [{"check": "connector_slack", "reason": "..."}],
"warnings": [{"check": "audience_persona", "reason": "reading_level missing"}],
"passed": ["required_identity", "voice_profile", ...]
}Behaviour rules
- Never print credential values. Connector probes use
--no-secrets; if a probe accidentally returns a credential in its error string, redact before printing. The skill output goes to logs and clipboards — assume it leaks. - Read-only. Never modify the brand profile, credentials, MCP config, or any persistent state. This is a checker, not a fixer. Hand back actionable next commands instead.
- Don't short-circuit. Run every check even after the first BLOCKER — agencies want the full punch list in one pass.
- Don't validate cross-brand. Per-brand only, by design. Looping across all brands is a separate workflow (
/digital-marketing-pro:agency-dashboard --health). - Idempotent. Running this skill twice in a row produces identical output (modulo timestamps). No retries inside the skill — retries are the user's call.
Arguments
/digital-marketing-pro:validate-profile [--brand <slug>] [--json] [--connectors <list>] [--quick]--brand <slug>— brand to validate (else uses active brand)--json— emit only the JSON summary, no human report (useful for chaining)--connectors <list>— comma-separated subset to probe instead of every connector in the profile (useful when only Slack rotated)--quick— skip the connector reachability probes (run only the field-level checks)
Related skills + commands
brand-setup— interactive brand creationimport-guidelines— bulk-load existing brand guidelines into the profilestatus— unified read-only snapshot of the active brandcheck— pre-publish content quality gateswitch-brand— set the active brandscripts/connector-status.py— the underlying connector health probescripts/resolve_model.py— model curator (used for currency check)
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

