CD proxies
Oxylabs proxy networks: Residential, Mobile, shared Datacenter/ISP, and Dedicated Datacenter/ISP proxies with geo-targeting, IP rotation, session persistence, and port-based sticky IPs. Use when routing traffic through proxies, building scrapers with proxy auth, rotating or sticky sessions, whitelisting IPs, or accessing geo-restricted content.
Oxylabs proxy networks: Residential, Mobile, shared Datacenter/ISP, and Dedicated Datacenter/ISP proxies with geo-targeting, IP rotation, session persistence…
As a process D 43/100 · Unfinished process — 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 · 10
✓ No critical or high findings
Medium and low: 10
-
low Exfiltration
net-credential-useexamples.md:10Credential used in a network call (verify the destination is the intended service) (test fixture / example file)curl -x ddc.…001 -U "user-$OXY_DC_USERNAME:$OXY_DC_PASSWORD" \
fixture -
low Exfiltration
net-credential-useexamples.md:38Credential used in a network call (verify the destination is the intended service) (test fixture / example file)curl -x disp…001 -U "user-$OXY_DC_USERNAME:$OXY_DC_PASSWORD" \
fixture -
low Exfiltration
net-credential-useexamples.md:44Credential used in a network call (verify the destination is the intended service) (test fixture / example file)curl -x disp…000 -U "user-$OXY_DC_USERNAME:$OXY_DC_PASSWORD" \
fixture -
low Exfiltration
net-credential-useexamples.md:63Credential used in a network call (verify the destination is the intended service) (test fixture / example file)curl -x 1.2.3.4:60000 -U "$OXY_DC_USERNAME:$OXY_DC_PASSWORD" \
fixture -
low Secrets in code
secret-high-entropy-tokenexamples.md:108High-entropy token-like string (may be an id, hash or a credential) (test fixture / example file; quoted — discussed, not commanded)-U "customer-$OXY_…23:$OXY_RES_PASSWORD" \
fixturequoted -
low Secrets in code
secret-high-entropy-tokenexamples.md:154High-entropy token-like string (may be an id, hash or a credential) (test fixture / example file; quoted — discussed, not commanded)proxy_user = f"customer-{username}-cc-…123"fixturequoted -
low Exfiltration
net-credential-useexamples.md:236Credential used in a network call (verify the destination is the intended service) (test fixture / example file)curl_setopt($ch, CURLOPT_PROXYUSERPWD, "customer-$username:$password");
fixture -
low Secrets in code
secret-high-entropy-tokenproxy-types.md:3High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)Each section lists endpoint, auth prefix, supported parameters, and best-fit use cases. Parameters append to username with hyphens: `cust…ASS`.
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:124High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)-U "customer-$OXY_…23:$OXY_RES_PASSWORD" \
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:131High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)-U "customer-$OXY_…-5:$OXY_RES_PASSWORD" \
quoted
Files scanned: 5. 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 43/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
- 30Running it twice. 1 mutating operations with no state check
- 60Tools and files. Uses tools (node) that frontmatter does not declare
- 100Steps. 7 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1552 tokens
- low 10 top-level sections: this looks like several domains in one skill
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
- +1No license
- +2Single-language instructions
- +3Description length 346: enough signal without eating the budget
- +4Structure: 11 headings
- +3Step-by-step instructions: 7 items
- +4Has examples (8 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 84.