BC freelance-pipeline-automation
Automated freelance pipeline manager for AI agents. Discovers jobs on Upwork, Fiverr, LinkedIn, and niche boards, scores leads by skill match (50%) + budget (30%) + recency (20%), generates personalized proposals, and tracks the full pipeline from discovery to payment. Commands: - freelance_pipeline.py add "Title" "$500" "python,api" Add new lead - freelance_pipeline.py score "Title" "$500" "python" Score without adding - freelance_pipeline.py digest Morning lead digest - freelance_pipeline.py status 3 proposal_sent Update lead status - freelance_pipeline.py list Show all leads JSON-based pipeline tracker with status states: new, qualified, proposal_sent, negotiating, accepted, paid, rejected. Python 3.8+, zero deps. Scoring thresholds: leads scoring 70+ are qualified for digest. Proposal generation includes matched skills analysis, budget assessment, and custom approach sections. Works with or without browser automation for gated sites.
As a process C 53/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The skill asks for more than the task needs: broad tool access, credential environment variables, binaries. Every extra permission widens the damage from a mistake or a compromise.
Narrow allowed-tools and the variable list to the minimum; replace binaries with readable sources or scripts.
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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
-
medium Broad scope
meta-broad-allowed-toolsSKILL.md:1Broad tool permissions pre-approved: Bashallowed-tools: Bash Read
Files scanned: 4. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 53/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 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
- 100Tools and files. Tools declared in frontmatter
- 100Steps. 8 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 429 tokens
- 100Running it twice. No mutating operations
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
- +4Description does not say when NOT to use the skill (false activations)
- +3Description length 1022: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +5Description quotes 2 example trigger phrases
- +4Structure: 6 headings
- +3Step-by-step instructions: 8 items
- +4Has examples (3 code blocks)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 77.