Home / Reports / ops-whatsapp-biz

ops-whatsapp-biz

Validated 11 Oct 2026 · Repository
Pro
0/ 100Poor
26 critical
11 warnings
14 suggestions
76 checks passed

Domain scores

Anti-Slop
70
Accessibility
100
Enterprise
100

Issues

Critical (26)

7.2-injection-riskline 69
Potential injection risk: unescaped variable in shell
Fix: Sanitize inputs and use parameterized commands
7.2-injection-riskline 88
Potential injection risk: unescaped variable in shell
Fix: Sanitize inputs and use parameterized commands
7.2-injection-riskline 89
Potential injection risk: unescaped variable in shell
Fix: Sanitize inputs and use parameterized commands
7.2-injection-riskline 118
Potential injection risk: unescaped variable in shell
Fix: Sanitize inputs and use parameterized commands
7.2-injection-riskline 125
Potential injection risk: unescaped variable in shell
Fix: Sanitize inputs and use parameterized commands
7.2-injection-riskline 127
Potential injection risk: unescaped variable in shell
Fix: Sanitize inputs and use parameterized commands
7.2-injection-riskline 141
Potential injection risk: unescaped variable in shell
Fix: Sanitize inputs and use parameterized commands
7.2-injection-riskline 146
Potential injection risk: unescaped variable in shell
Fix: Sanitize inputs and use parameterized commands
7.2-injection-riskline 206
Potential injection risk: unescaped variable in shell
Fix: Sanitize inputs and use parameterized commands
7.2-injection-riskline 208
Potential injection risk: unescaped variable in shell
Fix: Sanitize inputs and use parameterized commands
7.2-injection-riskline 215
Potential injection risk: unescaped variable in shell
Fix: Sanitize inputs and use parameterized commands
7.2-injection-riskline 219
Potential injection risk: unescaped variable in shell
Fix: Sanitize inputs and use parameterized commands
7.2-injection-riskline 222
Potential injection risk: unescaped variable in shell
Fix: Sanitize inputs and use parameterized commands
7.2-injection-riskline 232
Potential injection risk: unescaped variable in shell
Fix: Sanitize inputs and use parameterized commands
7.2-injection-riskline 233
Potential injection risk: unescaped variable in shell
Fix: Sanitize inputs and use parameterized commands
7.2-injection-riskline 239
Potential injection risk: unescaped variable in shell
Fix: Sanitize inputs and use parameterized commands
7.2-injection-riskline 250
Potential injection risk: unescaped variable in shell
Fix: Sanitize inputs and use parameterized commands
7.2-injection-riskline 256
Potential injection risk: unescaped variable in shell
Fix: Sanitize inputs and use parameterized commands
7.2-injection-riskline 266
Potential injection risk: unescaped variable in shell
Fix: Sanitize inputs and use parameterized commands
7.2-injection-riskline 283
Potential injection risk: unescaped variable in shell
Fix: Sanitize inputs and use parameterized commands
7.2-injection-riskline 285
Potential injection risk: unescaped variable in shell
Fix: Sanitize inputs and use parameterized commands
7.2-injection-riskline 294
Potential injection risk: unescaped variable in shell
Fix: Sanitize inputs and use parameterized commands
7.2-injection-riskline 309
Potential injection risk: unescaped variable in shell
Fix: Sanitize inputs and use parameterized commands
7.2-injection-riskline 368
Potential injection risk: unescaped variable in shell
Fix: Sanitize inputs and use parameterized commands
7.2-injection-riskline 370
Potential injection risk: unescaped variable in shell
Fix: Sanitize inputs and use parameterized commands
7.2-injection-riskline 374
Potential injection risk: unescaped variable in shell
Fix: Sanitize inputs and use parameterized commands

Warnings (11)

5.1-no-style-sectionline 1
No writing style section found
Fix: Add a '## Writing Style' or '## Anti-Slop' section
16.1-no-stop-conditionline 15
Complex skill lacks explicit stop conditions
Fix: Add stop/termination criteria (e.g., 'Stop after N iterations', 'Abort if error rate exceeds threshold')
16.2-no-guardrailsline 15
Skill uses Bash or destructive operations without safety guardrails
Fix: Add guardrails: specify forbidden commands, require confirmation for destructive actions, or use --dry-run patterns
2.3-date-sensitiveline 314
Date-sensitive content that may become stale
Fix: Use relative terms or update mechanisms
19.3-generator-no-output-specline 15
Generator pattern detected but no output format specified
Fix: Document the output format (template, schema, or example output)
19.5-pipeline-no-stagesline 15
Pipeline pattern detected but no stage documentation found
Fix: Document the pipeline stages, checkpoints, and data flow between stages
4.5-desc-no-triggersline 2
Description lacks triggering conditions
Fix: Add phrases like 'Use when...', 'Triggers on...', or 'Applies to...' to help Claude select this skill
1.2-desc-whatline 3
Description missing WHAT clause (action verb) - recommended by agentskills spec
Fix: Consider starting with what the skill does, e.g., 'Creates...', 'Generates...', 'Validates...'
1.2-desc-whenline 3
Description missing WHEN clause - recommended by agentskills spec
Fix: Consider adding 'Use when...' or 'Activate when...' to description
7.5-pii-detectedline 105
Potential international phone number detected in content
Fix: Use placeholder: +1-555-000-0000
12.3-workflow-vague-stepline 366
Step is too brief to be actionable: "Smoke test:"
Fix: Add specific details: what, where, and how

Suggestions (14)

5.2-no-do-dontline 1
Missing DO/DON'T lists for style guidance
Fix: Add explicit DO and DON'T lists for writing patterns
5.4-ai-vocabularyline 189
AI-vocabulary word detected: underscores
Fix: Replace with a plain word; these words cluster in LLM output
16.3-no-rollbackline 15
State-modifying skill lacks rollback or recovery guidance
Fix: Add rollback instructions: how to undo changes if something goes wrong (e.g., git revert, backup/restore steps)
16.4-no-idempotencyline 15
Skill does not document whether it is safe to re-run
Fix: Add idempotency guidance: state whether running the skill twice produces the same result or causes side effects
17.3-no-mode-awarenessline 15
Skill does not clarify standalone vs composed behavior
Fix: Clarify whether the skill works standalone, in pipelines, or both
17.4-no-interface-sectionline 15
Input and output contracts exist but lack a dedicated interface section
Fix: Add a ## Interface or ## I/O section to consolidate contract documentation
14.6-no-must-avoidline 1
No prohibitions or failure conditions found (nothing the skill must not do)
Fix: Add a short "Must not" or "Anti-patterns" list (e.g., 'never overwrite existing files', 'do not invent citations') so evaluators can write negative tests
3.4-gerund-namingline 2
Skill name could use gerund form for clarity
Fix: Consider gerund-style names like 'processing-pdfs' or 'analyzing-logs' (per best practices)
18.1-no-confidence-signalline 1
No confidence signal found for orchestrator decision-making
Fix: Add confidence indicators (e.g., confidence: high/medium/low) so orchestrators can route or retry
18.2-no-progress-signalline 1
Complex skill lacks progress reporting checkpoints
Fix: Add progress signals (e.g., 'Step 2 of 5: validating input') for long-running workflows
1.12-maxturns-not-skill-fieldline 12
maxTurns is a subagent field; Claude Code ignores it in SKILL.md
Fix: Remove maxTurns, or set it in a subagent definition and run the skill there with 'context: fork' and 'agent: <that subagent>'
1.19-non-portable-fieldline 4
Frontmatter keys outside the agentskills spec: argument-hint, effort, maxTurns. Claude Code loads the skill with them; claude.ai uploads and the Skills API reject it with 'Unexpected key(s)'
Fix: Nothing to do for Claude Code or plugin distribution. To upload to claude.ai or the Skills API, ship frontmatter with only name, description, license, compatibility, metadata and allowed-tools
7.6-limited-negative-casesline 1
Skill has minimal negative case coverage; consider adding: limitations/constraints, error handling, edge cases
Fix: Document failure modes, limitations, and edge cases for production-ready skills
12.4-no-troubleshootingline 15
Complex technical skill lacks troubleshooting section
Fix: Add a ## Troubleshooting section with Error/Cause/Fix table for common issues

OWASP Agentic (Cat 26)

Agent surface detected: declares tool beyond Read/Glob/Grep: Bash; declares tool beyond Read/Glob/Grep: Write; declares tool beyond Read/Glob/Grep: AskUserQuestion; performs consequential actions
1 warning 1 suggestion
  • 26.02-ASI02-unconstrained-bash warning Bash is granted with no constraint note (which commands, why)
    Fix: document which Bash commands the skill runs and why, or narrow the grant
  • 26.02-ASI02-over-grant suggestion 5 tools declared with no per-tool rationale
    Fix: add a one-line rationale per tool, or trim the set to the minimum the task needs
ASI-01: skippedASI-02: failASI-03: skippedASI-04: skippedASI-05: skippedASI-06: skippedASI-07: skippedASI-08: skippedASI-09: skippedASI-10: skippedASI-11: skipped

Badges

skillcheck ✕ passed skillcheck ✕ antislop 100 skillcheck WCAG AA skillcheck WCAG AAA skillcheck enterprise

Get a report like this for your own skill

Run the free validator to see your score in seconds. Pro adds the substance checks: anti-slop, security, accessibility and agent readiness.