GLSL Encyclopedia

v0.1.0

GLSL language/specification workflow for GLSL-specific questions, shader authoring and review, exact syntax and semantic lookup, built-in and qualifier refer...

0· 46·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description (GLSL reference, authoring, review) align with the behavior: consult official GLSL docs, cache consulted pages, and keep local notes. The two included helper scripts (caching and workspace init) are directly relevant.
Instruction Scope
SKILL.md confines actions to consulting docs.vulkan.org, checking and writing a local cache under `.GLSL-Encyclopedia/`, and inspecting local shader state. It does not instruct reading unrelated system files or exfiltrating data to arbitrary endpoints.
Install Mechanism
No install spec; this is instruction-first with two small Python helper scripts. No external downloads or package installs are requested.
Credentials
No environment variables, credentials, or external service tokens are required. Network access is limited by code to docs.vulkan.org (https) only, which matches the stated purpose.
Persistence & Privilege
The skill does not request always:true, does not alter other skills' configs, and only writes to a workspace-local `.GLSL-Encyclopedia/` directory. It does allow normal autonomous invocation (platform default).
Assessment
This skill appears coherent and limited to caching and consulting the official GLSL docs. Before installing or running: (1) be aware the scripts will write/seed files under a `.GLSL-Encyclopedia/` directory in the chosen working directory (you can set a different root when running the scripts), (2) the caching script makes HTTPS requests but is coded to only accept docs.vulkan.org URLs, and (3) review the two included Python scripts if you want to confirm there are no local-path or symlink edge cases in your environment. No credentials or broad system access are requested, but if you are concerned about network or filesystem side effects, run the scripts in an isolated/project directory or inspect and run them manually rather than allowing autonomous agent execution.

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

latestvk97fy2964gm129f08g6k8qh7q183qhbp

License

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

Runtime requirements

🎨 Clawdis

Comments