validate-profile

Validates brand profile completeness, connector configuration, and compliance coverage before campaign execution.

787|132|Updated Feb 11, 2026
One-click install
npx skills add https://github.com/indranilbanerjee/digital-marketing-pro --skill validate-profile
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: validate-profile
Source: https://github.com/indranilbanerjee/digital-marketing-pro/tree/main/skills/validate-profile
Command: npx skills add https://github.com/indranilbanerjee/digital-marketing-pro --skill validate-profile

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Brand profiles and API credentials drift constantly across multi-brand portfolios, and running a long engagement on a broken profile wastes hours of rework. This Skill performs a read-only health check that confirms a brand profile is complete and every referenced connector is configured before production work begins.

Core Features & Use Cases

  • Profile Field Validation: Checks required identity fields, voice profile, audience persona, guardrails, and compliance-jurisdiction coverage, reporting each as BLOCKER or WARNING.
  • Credential-Safe Connector Probes: Verifies connector configuration and MCP server reachability via connector-status.py without ever printing credential values.
  • Environment Checks: Confirms output-path writeability and model-registry currency, then emits a structured report plus machine-readable JSON summary.
  • Use Case: After rotating a Slack API key, run the check to confirm the new credential is wired up and the profile still passes before launching a campaign.

Quick Start

Ask the AI to validate the active brand profile and confirm all connectors and credentials are correctly configured before running an engagement.

Frequently Asked Questions about validate-profile

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check if a brand profile is ready before running a campaign?

Run the validate-profile check against the brand slug or active brand. It inspects required identity fields, voice profile, guardrails, compliance jurisdictions, connectors, and output paths, then reports each item as OK, WARNING, or BLOCKER with a final pass or blocked decision.

How to verify API connector credentials without exposing secrets?

The skill probes connectors through connector-status.py with --probe-only and --no-secrets flags, which confirm environment variables and MCP entries exist without printing values. It reports config-level status classes like CONFIGURED or MISSING_ENV rather than live responses.

Does the validation modify the brand profile or credentials?

No, the check is strictly read-only and never modifies profiles, credentials, MCP config, or any persistent state. It returns actionable next commands for the user to fix issues instead of attempting repairs itself.

What happens when a compliance jurisdiction is missing from the profile check?

If a declared target jurisdiction has no matching entry in the compliance rules reference, the check reports a BLOCKER stating that engagement would produce non-compliant deliverables. The issue must be resolved before running engagement or campaign commands.

Why does validation fail on a freshly created brand profile?

Earlier versions checked only legacy field names like target_jurisdictions and voice, while brand-setup writes target_markets and brand_voice. The current validator accepts both naming conventions, so update the skill if fresh profiles fail on BLOCKER.

Can I validate only specific connectors after rotating one API key?

Yes, pass the --connectors argument with a comma-separated subset to probe only those connectors instead of every one in the profile. The --quick flag skips reachability probes entirely and runs only field-level checks.