BB editorial-chief-workflow
Coordinate multi-agent editorial and publishing work as a chief editor using a dynamic strategy-loading workflow. Use when planning topics, decomposing content-production tasks, assigning writing/design/review/layout work, enforcing business-goal alignment, and delivering final review-ready files into the real Obsidian publication directory. This skill requires two execution parameters: target audience and publication channel. If either is missing, ask before proceeding. Then load the matching audience profile and channel strategy from references before assigning agents or accepting results.
Coordinate multi-agent editorial and publishing work as a chief editor using a dynamic strategy-loading workflow.
As a process B 70/100 · Nearly there — weak spots: result and completion, when it triggers, inputs and preconditions
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 · 0
✓ No critical or high findings
Files scanned: 6. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Nested mappings are not allowed in compact mappings at line 2, column 14: description: Coordinate multi-agent editorial and publishing work as a chief ed… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value
Process rating: all ten parameters 70/100
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 5 mutating operations with no state check
- 40Result and completion. Does not say what the result is
- 100Tools and files. No external tools needed
- 100Steps. 108 steps
- 100Failures and branches. 1 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2092 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)
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +3Description length 598: enough signal without eating the budget
- +4Structure: 55 headings
- +3Step-by-step instructions: 108 items
- +4Reference files are cited in the instructions (1 of 1)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 74.