Architecture Quantum Analyzer

v1.0.0

Analyze a system's architecture quanta — independently deployable units with distinct quality attribute needs. Use this skill whenever the user needs to dete...

0· 59·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/description match the runtime instructions: the skill inspects codebases and deployment/config files to determine independently deployable units. It does not request unrelated binaries, credentials, or config paths.
Instruction Scope
SKILL.md directs the agent to scan repository structure, deployment manifests, imports, and DB configs — all relevant to identifying quanta. There are no instructions to contact external endpoints or to collect system-wide secrets beyond what exists in the provided codebase or description.
Install Mechanism
No install spec and no code files are included (instruction-only). This minimizes written-to-disk risk and matches the described behavior.
Credentials
The skill requests no environment variables or credentials, which is proportionate. Note: the analysis explicitly reads code, deployment, and DB config files — if those contain credentials or secrets, the agent will see them. That exposure is a natural consequence of codebase analysis, not an incoherence in required permissions.
Persistence & Privilege
always is false and autonomous invocation is allowed (platform default). The skill does not declare persistence, system-wide config changes, or elevated privileges.
Assessment
This skill is instruction-only and coherent for the stated purpose. Before running it, be aware it will examine whatever codebase or configuration you provide — including any secrets or credentials stored in repo files or deployment configs. If you don't want sensitive data inspected, either sanitize the repository/configs or provide a high-level system description instead of full source. You can also review the referenced GitHub homepage for provenance and consider running the analysis locally or in a controlled environment. The skill may call the companion skill 'architecture-characteristics-identifier' if component quality attributes are unknown; verify that secondary skill before granting broader access.

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

architecturevk970y5xg5s3rsfjsq1err01de184qbx8bookforgevk970y5xg5s3rsfjsq1err01de184qbx8connascencevk970y5xg5s3rsfjsq1err01de184qbx8couplingvk970y5xg5s3rsfjsq1err01de184qbx8deploymentvk970y5xg5s3rsfjsq1err01de184qbx8latestvk970y5xg5s3rsfjsq1err01de184qbx8monolith-vs-distributedvk970y5xg5s3rsfjsq1err01de184qbx8quantumvk970y5xg5s3rsfjsq1err01de184qbx8software-architecturevk970y5xg5s3rsfjsq1err01de184qbx8

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Runtime requirements

📚 Clawdis

Comments