BD dev-factory
Automated software development agent using ChatDev 2.0 and GLM-5. Discovers topics from GitHub Trending, CVE databases, and security news → generates code with 7-agent ChatDev team → tests automatically → publishes to GitHub. Self-correction loop (error → fix → retry, max 3 times). Use when you want to automate development, create security tools, or generate DevOps utilities. Triggers: "자동 개발", "도구 생성", "builder agent", "chatdev".
As a process D 39/100 · Unfinished process — 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 contains commands that delete files, rewrite disks or execute code fetched from the network. The agent may run them without asking if it believes the instructions require it.
Replace destructive commands with safe equivalents that ask for confirmation, scope them to one folder, and stop piping curl into a shell: pin a version and a checksum.
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 · 15
✓ No critical or high findings
Medium and low: 15
-
medium Dangerous commands
cmd-persistencecheck_status.py:160Persistence mechanism (cron / launchd / scheduled task / autorun registry) (string literal in code, not executed)print(" launchctl unload ~/Library/LaunchAgents/com.openclaw.builder-*.plist")code literal -
medium Dangerous commands
cmd-persistencecheck_status.py:163Persistence mechanism (cron / launchd / scheduled task / autorun registry) (string literal in code, not executed)print(" launchctl load ~/Library/LaunchAgents/com.openclaw.builder-*.plist")code literal -
low Risky intent
intent-offensive-securityDISCOVERY_REPORT.md:41Offensive-security / dual-use content (legitimate for authorised testing; review intended use)2. **Security Tool: Ransomware Detector** (Security News)
-
low Risky intent
intent-offensive-securitydiscovery-integration.md:142Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (detector / deny-list definition)return "Ransomware Detector"
detector -
low Risky intent
intent-offensive-securityIMPROVEMENT_ANALYSIS.md:99Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (quoted — discussed, not commanded)keywords = ['ransomware', 'vulnerability', 'malware', 'phishing']
quoted -
low Risky intent
intent-offensive-securityLIVE_EXECUTION_REPORT.md:48Offensive-security / dual-use content (legitimate for authorised testing; review intended use)2. Security Tool: Ransomware Detector (0.62점)
-
low Risky intent
intent-offensive-securityLIVE_EXECUTION_REPORT.md:125Offensive-security / dual-use content (legitimate for authorised testing; review intended use)### 2. Security Tool: Ransomware Detector
-
low Risky intent
intent-offensive-securityLIVE_EXECUTION_REPORT.md:129Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (detector / deny-list definition)"title": "Security Tool: Ransomware Detector",
detector -
low Risky intent
intent-offensive-securityLIVE_EXECUTION_REPORT.md:139Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (detector / deny-list definition)- Severity: 0.80 (ransomware)
detector -
low Risky intent
intent-offensive-securityOPERATION_START.md:84Offensive-security / dual-use content (legitimate for authorised testing; review intended use)✅ Security Tool: Ransomware Detector
-
low Risky intent
intent-offensive-securityOPERATION_START.md:182Offensive-security / dual-use content (legitimate for authorised testing; review intended use)- ransomware
-
low Dangerous commands
cmd-cron-mentionOPERATION_START.md:249Mentions editing / listing crontab (documentation of a security skill)1. ✅ Cron job 수동 설정 (crontab -e)
security skill -
low Risky intent
intent-offensive-securityPRODUCTION_DEPLOYMENT.md:85Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (quoted — discussed, not commanded)"keywords": ["ransomware", "vulnerability", "malware", "phishing"],
quoted -
low Exfiltration
read-dotenvSKILL.md:103Reads a .env file (documentation of a security skill)cp .env.example .env
security skill -
low Risky intent
intent-offensive-securityTEST_RESULTS.md:48Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (test fixture / example file)2. **Security Tool: Ransomware Detector** (점수: 0.62)
fixture
Files scanned: 50. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Nested mappings are not allowed in compact mappings at line 2, column 14: description: Automated software development agent using ChatDev 2.0 and GLM-5. … ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value
Process rating: all ten parameters 39/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. 2 mutating operations with no state check
- 40Consistency. Frontmatter name (dev-factory) differs from the folder (dev-factory-repo)
- 60Tools and files. Uses tools (python) that frontmatter does not declare
- 100Steps. 33 steps
- 100Execution cost. Instruction body is 1519 tokens
- low 14 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
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- -2localhost URLs: will not work for another user
- +1No license
- +2Single-language instructions
- +5Description quotes 2 example trigger phrases
- +3Description length 434: enough signal without eating the budget
- +4Structure: 38 headings
- +3Step-by-step instructions: 33 items
- +4Has examples (18 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 77.