Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →ferroxlabs/wayland-pipeline-batch-review
Friday pipeline review: resolve a pipeline data source, scan deal records to identify stuck deals past a staleness threshold, and draft quick forensics on the top three.
Passed 16 of 21 test cases with the skill, and 12 of 21 without it.
and 8 more in the full report
7 fixed10 passed either way3 still failing3 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 7 test cases the skill fixed. Same model, same prompt, with and without the skill.
We have a local directory at '/var/data/deals' with CSV files and a connected HubSpot integration. I've also uploaded 'q3_deals.csv' into the chat workspace. Which data source should be evaluated for the stalled opportunity scan?
| Checked | Without skill | With skill |
|---|---|---|
| Selects the attached workspace file 'q3_deals.csv' as the primary data source. | Missed | Passed |
The instructions your model reads when the skill loads.
Estimated time: about 60 seconds
This workflow is a fast, mostly deterministic pipeline sweep. It resolves a pipeline data source, identifies the deals that have not advanced past a staleness threshold, and drafts quick forensics on the top three stuck deals. The output is a list of stuck deals plus first-pass forensics.
Data input resolution. Before scanning, resolve the pipeline source in this order, first hit wins:
If none of these yields data, halt and ask the user to attach an export or connect HubSpot. Never fabricate deals to fill an empty review.
Inputs. Confirm two inputs before scanning: the pipeline directory (used only when no attached export or HubSpot connector is available, required) and the staleness threshold in days (default 14; days without advancement past this count a deal as stuck).
Step 1: Scan for Stuck Deals (uses: sales-report)
Resolve the pipeline source per the resolution order above, then scan the deal records to identify the stuck deals: those that have not advanced in more than the staleness threshold number of days. If the source resolves to no data, halt and ask the user to attach an export or connect HubSpot rather than continuing. Output the list of stuck deals.
test cases passed, vs 12 / 21 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.