ECCSystem
v1.0.0Everything Claude Code (ECC) system integration - 30 agents, 77 rules, 12 languages, 4 iron laws, TDD workflow, verification gates
⭐ 1· 35·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
medium confidencePurpose & Capability
Name/description (ECC orchestration, TDD, multi-agent reviews) match the SKILL.md content: policies, workflows, agent roles, and commands to run local tooling. The skill is instruction-only and asks for no credentials or installs, which is appropriate for a policy/orchestration guideline.
Instruction Scope
Instructions assume access to the repository and to project-local scripts (e.g., tools/language-detector.py, ecc-hooks-adapter.py) and instruct the agent to run/aggregate agents and verify tests/coverage/security. That is coherent for a code-review/TDD helper, but it means the agent will need to read project files and may invoke local scripts — confirm you are comfortable with the agent inspecting/executing your repo contents.
Install Mechanism
No install spec and no code files are provided. This is lowest-risk from install perspective; nothing is downloaded or written by the skill itself.
Credentials
Skill declares no required environment variables, secrets, or config paths. However, SKILL.md requires checking code for hardcoded secrets and running project scripts — this implies local file access but does not request external credentials, which is proportionate.
Persistence & Privilege
always is false and the skill does not request system-wide changes or modify other skills. Model invocation is allowed (normal). No elevated persistence or privileged config changes are requested.
Assessment
This skill is a policy and workflow template, not executable code: it will ask the agent to inspect your repository and to run project-local scripts (examples reference tools/ and docs/ paths that are not included in the skill). Before enabling: 1) review SKILL.md in full to ensure the described scripts and paths exist in your projects (or remove/adjust references); 2) ensure you are comfortable with an agent reading and running files from your repo (it may execute project scripts); 3) confirm test/coverage/security tooling is present so the agent's verification steps are meaningful; 4) note the skill source is 'unknown' — if you need stronger assurance, ask the publisher for provenance or a signed release. Because there are no included code files, static scanners had nothing to analyze — a manual review of the SKILL.md and your repository is recommended before use.Like a lobster shell, security has layers — review code before you run it.
latestvk977a8xgzy6jd4w99m12dgrrvd845exv
License
MIT-0
Free to use, modify, and redistribute. No attribution required.