ClawHub

Component Identifier

v1.0.0

Decompose a system into well-defined components using structured discovery techniques. Use this skill whenever the user is designing a new system from requir...

⭐ 0· 50·0 current·0 all-time
byHung Quoc To@quochungto
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
Capability signals
CryptoCan make purchases
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
Name and description match the instructions: the skill guides decomposition of systems and asks for requirements, actors, workflows, and (if present) the existing codebase. There are no unrelated env vars, binaries, or configuration paths declared.
ℹ
Instruction Scope
The SKILL.md explicitly instructs the agent to inspect 'existing codebase' and to use Read/Write (and optionally Grep/Glob) to discover package/service structure. That is appropriate for this purpose, but it means the agent may read repository files and write analysis outputs — confirm what directories are in-scope and avoid scanning secrets or unrelated configuration files.
✓
Install Mechanism
There is no install spec and no code files; the skill is instruction-only, which minimizes on-disk risk.
✓
Credentials
The skill declares no environment variables, credentials, or config paths. Its need to read a codebase (via agent tools) is proportional to its purpose; there are no unexplained secrets or unrelated credential requests.
✓
Persistence & Privilege
always is false and the skill does not request persistent or elevated agent-wide privileges. It does not attempt to modify other skills or global agent settings in the provided instructions.
Assessment
This skill appears coherent: it will ask for system requirements and may request to read your codebase to identify components. Before using it, decide which repository paths are safe to expose (avoid scanning directories with secrets, keys, or sensitive configs), confirm whether you want the agent to write analysis artifacts into the repo or a separate output location, and be aware it may reference results from the related 'architecture-characteristics-identifier' skill. If you have sensitive files in your workspace, restrict the agent's Read access or provide sanitized inputs (requirements and representative code samples) instead of full repository access.

Like a lobster shell, security has layers — review code before you run it.

architecturevk9760gbh22f2rv5n4qefkvp51n84pjkybookforgevk9760gbh22f2rv5n4qefkvp51n84pjkycomponentsvk9760gbh22f2rv5n4qefkvp51n84pjkydecompositionvk9760gbh22f2rv5n4qefkvp51n84pjkydomain-driven-designvk9760gbh22f2rv5n4qefkvp51n84pjkylatestvk9760gbh22f2rv5n4qefkvp51n84pjkymodularityvk9760gbh22f2rv5n4qefkvp51n84pjkysoftware-architecturevk9760gbh22f2rv5n4qefkvp51n84pjky

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Runtime requirements

📚 Clawdis

Comments