DC dealwork
Work marketplace where Humans and AI Agents hire each other. Find jobs, place bids, deliver work, get paid.
Work marketplace where Humans and AI Agents hire each other.
As a process C 53/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
The same skill appears in 1 more place: ClawHub
What is at stake
The skill contains fragments that, in the wrong hands, cost money or data. Below: what the installer risks and what the author should do.
The files contain someone else's key or token. If it is live, your agent will call third-party services under a stranger's identity; if it was revoked, the skill's scripts simply fail. Such a key often arrives with the author's whole workspace, personal data included.
The key is visible to everyone who downloaded the skill and has likely been copied by catalog-scanning bots already. Revoke it now, check bills and access logs, then reissue.
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
- Address the high-severity findings: each costs 18 safety points. If one is a false positive, add the rule id to guard.allow in spec.yaml.
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- 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 · 19
-
high Secrets in code
meta-credential-filescredentials.jsonCredential / dotenv files bundled with the skill (1)credentials.json
Medium and low: 18
-
medium Broad scope
meta-agent-memory-dumpHEARTBEAT.mdAgent memory / workspace files bundled with the skill (4) — likely a workspace dump with personal data or tokensHEARTBEAT.md, IDENTITY.md, MEMORY.md, SOUL.md
-
low Secrets in code
secret-high-entropy-tokendealwork-deliverables/deliverable-payload.json:1High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded){"description": "Minimal UI / MUI reusable UX/UI skill package for Claude & Codex. Includes main skill files, detailed rules, prompt/output examples, and a runnable Next.js/TypeScript sample page.", "quoted -
low Secrets in code
secret-high-entropy-tokendealwork-deliverables/revised-deliverable-payload.json:1High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded){"description": "Revised Minimal UI / MUI UX/UI skill package.\n\nChanges made in response to the revision request (16/07/2026):\n- Added a dedicated \"Dashboard layout (critical)\" section to rules/0quoted -
low Obfuscation
obf-base64-blobgmail_cleanup.py:8Long base64-looking blob (quoted — discussed, not commanded)API_KEY = "v2.f…7vS"
quoted -
low Secrets in code
secret-password-literalgmail_cleanup.py:8Hard-coded password / key literal (may be an example)API_KEY = "v2.f…7vS"
-
low Obfuscation
obf-base64-blobgmail_finish.sh:3Long base64-looking blob (quoted — discussed, not commanded)export MATON_API_KEY="v2.f…7vS"
quoted -
low Obfuscation
obf-base64-blobgmail_finish2.sh:3Long base64-looking blob (quoted — discussed, not commanded)export MATON_API_KEY="v2.f…7vS"
quoted -
low Obfuscation
obf-base64-blobgmail_organize_targeted.py:12Long base64-looking blob (quoted — discussed, not commanded)"MATON_API_KEY": "v2.f…7vS",
quoted -
low Obfuscation
obf-base64-blobgmail_organize.py:10Long base64-looking blob (quoted — discussed, not commanded)API_KEY = "v2.f…7vS"
quoted -
low Secrets in code
secret-password-literalgmail_organize.py:10Hard-coded password / key literal (may be an example)API_KEY = "v2.f…7vS"
-
low Exfiltration
exfil-secret-in-urlSKILL.md:143Credential passed in a URL query string (normal for some APIs — verify the host is the intended service) (the skill's own vendor host; quoted — discussed, not commanded)RESULT=$(curl -s "https://dealwork.ai/api/v1/agents/connect/status?token=…")
vendor-hostquoted -
low Exfiltration
net-credential-useSKILL.md:143Credential used in a network call (verify the destination is the intended service) (the skill's own vendor host)RESULT=$(curl -s "https://dealwork.ai/api/v1/agents/connect/status?token=…")
vendor-host -
low Exfiltration
net-credential-useSKILL.md:289Credential used in a network call (verify the destination is the intended service) (the skill's own vendor host)curl -s https://dealwork.ai/api/v1/jobs -H "Authorization: Bearer $API_KEY"
vendor-host -
low Dangerous commands
cmd-background-processSKILL.md:477Starts a background / autostarted processnohup node ~/.openwork/openwork-worker.js --daemon > ~/.openwork/worker.log 2>&1 &
-
low Dangerous commands
cmd-background-processSKILL.md:529Starts a background / autostarted processnohup node ~/.openwork/openwork-worker.js --daemon > ~/.openwork/worker.log 2>&1 &
-
low Dangerous commands
cmd-background-processSKILL.md:550Starts a background / autostarted processnohup node ~/.openwork/openwork-worker.js --daemon > ~/.openwork/worker.log 2>&1 &
A further 2 matches are quotations in this security skill's documentation and are not counted as findings.
Files scanned: 55. 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") - warning
body-longSKILL.md body ≈ 15196 tokens (recommended < 5000); move details to references/ - note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 53/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 20When it triggers. No condition that starts the skill
- 40Result and completion. Does not say what the result is
- 40Consistency. Frontmatter name (dealwork) differs from the folder (polymarket-edge-scanner)
- 40Execution cost. Instruction body is 15196 tokens: crowds the task out of the window
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 85Steps. 135 steps, 1 vague phrases
- 100Failures and branches. 2 branches, has a failure section
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 15 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)
- +3Description length 107: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +4Structure: 73 headings
- +3Step-by-step instructions: 135 items
- +4Has examples (63 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 58.