AC crewai-workflows
Execute AI-powered crew workflows for marketing content generation, customer support handling, data analysis, and social media calendar creation. Use when tasks involve (1) creating marketing content, taglines, or campaigns, (2) handling customer support inquiries or responses, (3) analyzing business data for insights, (4) generating comprehensive social media content calendars, or (5) any content generation or analysis task that benefits from specialized AI crew workflows. Workflows are powered by DeepSeek, Perplexity, and Gemini models.
As a process C 60/100 · Has gaps — weak spots: when it triggers, failures and branches, running it twice
How to improve
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 1
✓ No critical or high findings
Medium and low: 1
-
low Secrets in code
secret-high-entropy-tokenSKILL.md:15High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)export CREWAI_API_KEY="5aZy…dST"
quoted
Files scanned: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 60/100
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 1 mutating operations with no state check
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 32 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1219 tokens
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +1No license
- +2Single-language instructions
- +3Description length 544: enough signal without eating the budget
- +4Structure: 14 headings
- +3Step-by-step instructions: 32 items
- +3Output format is stated explicitly
- +4Has examples (10 code blocks)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 90.