AF workflow-chain
Chain multiple pipeline scripts into a single sequential or parallel workflow. Acts as a "playlist" for PrecisionLedger pipeline scripts. Use when a task requires multiple pipelines in sequence (e.g., "full close + analysis package for Paulson") or when building reusable workflow templates for recurring multi-step client work. Reads the pipeline manifest and client SOPs to auto-detect which pipelines apply. Can run ad-hoc chains or saved templates. NOT for: single-pipeline tasks (use the specific skill), non-pipeline work (email, web search, content creation), or tasks that don't involve QBO data or pipeline scripts.
As a process F 54/100 · Will not run — References files that are not bundled: scripts/pipelines/, scripts/pipelines/manifest.json
How to improve
- The text references files that are not there: add them or drop the references.
- 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: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: scripts/pipelines/ - warning
missing-refreference to a missing file: scripts/pipelines/manifest.json
Process rating: all ten parameters 54/100
- 0Tools and files. 2 referenced file(s) missing: scripts/pipelines/, scripts/pipelines/manifest.json
- 0Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 1 mutating operations with no state check
- 50When it triggers. No condition that starts the skill
- 60Result and completion. Output format stated, no completion criterion
- 85Steps. 35 steps, 1 vague phrases
- 100Failures and branches. 2 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2221 tokens
- 100Progress reporting. Reports progress
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
- +2Single-language instructions
- +5Description quotes 2 example trigger phrases
- +4Description says when NOT to use the skill
- +3Description length 624: enough signal without eating the budget
- +4Structure: 22 headings
- +3Step-by-step instructions: 35 items
- +3Output format is stated explicitly
- +4Has examples (9 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 88.