HYPER-ADVANCE SKILL MATRIX
v3.0.0Master executive-level tech leadership with expertise in multi-cloud, scalable architecture, AI/ML systems, security, and $500M+ impact delivery for CTO/VPE...
⭐ 0· 12·0 current·0 all-time
by@kosasih
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
Capability signals
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
OpenClaw
Benign
high confidencePurpose & Capability
The name and description (CTO/VPE-level leadership, architecture, multi-cloud, AI/ML, security) match the SKILL.md content, which is a long-form framework and guidance document. There are no unexpected required binaries, environment variables, or install steps that would be out of scope for a documentation/assistant skill.
Instruction Scope
SKILL.md is self-contained guidance and examples for executive-level advice. It does not instruct the agent to read system files, access environment variables, call external endpoints, or perform side-effecting system operations. The instructions are focused on producing advisory output rather than collecting or transmitting unrelated data.
Install Mechanism
There is no install spec and no code files — this is an instruction-only skill. That minimizes risk from downloads or on-disk executables.
Credentials
The skill requires no environment variables, credentials, or configuration paths. That is proportionate for a purely informational/assistant skill that provides strategic guidance.
Persistence & Privilege
always is false (normal), and model invocation is allowed (default). The skill does not request persistent presence or modifications to other skills or system-wide settings.
Assessment
This skill is essentially a content-only CTO/VP-level playbook and appears coherent and low-risk: it doesn't install software or ask for credentials. Two practical cautions before installing or using it: (1) provenance — the source and homepage are missing, so if you need traceability or legal/attribution guarantees prefer skills with a verifiable publisher; (2) accuracy/privacy — treat recommendations as advisory (verify technical claims independently) and avoid pasting sensitive proprietary data into prompts because the skill will see whatever you send it. If you plan to integrate this guidance into automation that touches your systems, create a separate, auditable process and only use skills that explicitly declare the required credentials and scopes.Like a lobster shell, security has layers — review code before you run it.
latestvk97e4g85dygjzbhftf6wbecz1984b26b
License
MIT-0
Free to use, modify, and redistribute. No attribution required.