Agent skill · Audited from source
web-shader-extractor
skill · lixiaolin94/skillsLicence not declaredAudited 20 Oct 2026 · source 584a6ee62212
Is it safe? Yes — SAFE, grade B (89/100). We read this skill's source at commit 584a6ee62212 and found no filesystem, network or shell access and no hard-coded secrets. What it does: Use when a user gives or references a webpage URL and wants to extract, reproduce, port, or locally replay a WebGL, WebGPU, Canvas, shader-like, animated background, interactive 3D, or web visual effect. Locks the…
Cite
Cite this page
ModelsAtlas. “web-shader-extractor (lixiaolin94/skills)”. Retrieved 20 Oct 2026. https://modelsatlas.com/skills/lixiaolin94/web-shader-extractor
Trust audit
Audit 0.4.1 · source read 20 Oct 2026
SAFE means nothing in the source contradicts what the skill says it does. Grade B is shared by 13,985 of 14,816 audited skills.
What the source does
- FilesystemNone observedNo reads or writes in the source
- NetworkNone observedNo outbound calls in the source
- ShellNone observedNo commands run in the source
- DependenciesPinnedNothing floats
- SecretsNone foundNo keys in source
Five audit layers
| Layer | What we check | Result | Findings |
|---|---|---|---|
L0 Provenance | Repo owner, licence, archive status, activity | PASS | 1 |
L1 Static source | Secrets, path traversal, supply chain, hidden code | PASS | 0 |
L2 Instructions | Prompt injection, authority framing, hidden directives | PASS | 1 |
L3 Inventory | The files and declarations match the source | PASS | 0 |
L4 Sandbox | Run in isolation and watch behaviour | SKIPPED why | 0 |
Gates applied: no behavioural pass, no license.
Findings (2)
LOWInventory / provenanceinv.no_license
- Why
- no LICENSE file and no repo licence
- Fix
- add a licence
INFOPrompt injectionprompt.credential_read · references/evidence-policy.md:93
Do not persist cookies, Authorization headers, access tokens, private API keys, or private account data.
- Why
- asks the agent to read credentials
- Fix
- —
Audit 0.4.1 · source sha 584a6ee62212 · 20 Oct 2026Report an issue or request a re-scan
Provenance
Who published it, and what the verdict is pinned to
- Publisherlixiaolin94 GitHub userOwner of the repository this skill is read from
- Source folderlixiaolin94/skills/web-shader-extractorThe exact folder we audited
- LicenceNot declaredAs the repository states it
- Commit pinned for this verdict584a6ee62212A new audit runs when the source changes
- Repository statusNot archivedLast push 109 days ago
- Sandboxed runNot runSkills are read, not executed; layer L4 is skipped
What it tells the agent
Full source on GitHub ↗Its description: Use when a user gives or references a webpage URL and wants to extract, reproduce, port, or locally replay a WebGL, WebGPU, Canvas, shader-like, animated background, interactive 3D, or web visual effect. Locks the…
--- name: web-shader-extractor description: > Use when a user gives or references a webpage URL and wants to extract, reproduce, port, or locally replay a WebGL, WebGPU, Canvas, shader-like, animated background, interactive 3D, or web visual effect. Locks the target rendering surface group, records shader/resource/render graph/timing/input evidence, builds an evidence-matched local baseline, then projectizes it. Do not use for ordinary DOM/CSS page cloning. --- # Web Shader Extractor Index for WebGL / WebGPU / Canvas rendering investigation and local replay. Start from the target visual. Lock the surface group. Trace source or runtime facts. Build a runnable baseline. Then projectize. ## Router Contract This file is the index. Do not treat it as the full operating manual. Before task action, read: - `references/operating-contract.md` - `references/recon-kernel.md` Then load only the focused references needed by the current state. Keep large evidence, captures, and generated outputs out of the conversation. Store them in the user's output directory. ## Use This For - Extracting a webpage WebGL, WebGPU, Canvas2D, OffscreenCanvas, shader, or animated canvas effect. - Replaying an animated background, product shader, interactive WebGL scene, or Canvas visual locally. - Building an evidence-matched baseline first, then an editable project. - Investigating target-bound shader/render graph/timing/resource/input facts. Do not use this for ordinary DOM/CSS cloning, static screenshots, generic website copying, unrelated JavaScript deobfuscation, or product UI redesign. Use it only when the task has a shader/canvas target. ## Core Rules - Target-bound before framework-bound: a global Three.js, platform, or shader signature is only a hypothesis until tied to the target surface group. - Probes must discriminate: before running a probe, state which live hypotheses it separates and what each outcome eliminates. Evidence consistent with every candidate is weak; evidence only one candidate predicts is strong. - Evidence before implementation: source, runtime objects, frame captures, source maps, and public structured definitions outrank visual fitting. - No fabricated numbers: confidence is expressed with hypothesis status and `SOURCE`/`PARTIAL`/`GUESS`, never invented probabilities or scores. - Baseline before projectization: never overwrite a verified baseline for cleanup, simplification, or native conversion. - Honest labels: implementation-critical facts are `SOURCE`, `PARTIAL`, or `GUESS`; unlabeled values are treated as `GUESS`. - No compensation tuning: do not adjust brightness, time, color, offsets, or noise to mask missing pipeline evidence. - Gate artifacts are transition guards: if the required artifact is missing, incomplete, or has placeholders in gate-critical fields, the state has not advanced. - Ask only for product scope changes or external access/permission blockers. - Use plain records: state the fact, evidence path, current unknown, and next action. Avoid metaphor, broad claims, and unsupported conclusions. ## State Router The full state machine, branches, and gate semantics live in `references/recon-kernel.md`. The gate order is fixed: `TARGET_LOCKED` must precede deep source/bundle work. Before lock, only narrow source probes tied to `nextProbe` are allowed. `REPLAY_READY` must precede implementation. `BASELINE_VERIFIED` must precede projectization. ## Reference Router Load only what the current state needs: | Need | Read | |---|---| | Global contract, fact labels, completion states | `references/operating-contract.md` | | Kernel, initial protocol, state flow, autonomy, budgets | `references/recon-kernel.md` | | Surface discovery and visual attribution | `references/surface-discovery.md` | | Lock criteria, target-bound evidence, scope, Three.js binding | `references/target-lock.md` | | Evidence labels, ledgers, unknown classes, sensitive data | `references/evidence-policy.md` | | Tool capability selection | `references/tool-capability-matrix.md` | | WebGL, WebGPU, and Canvas2D capture facts | `references/capture-backends.md` | | Source maps, bundle slices, config, encoded definitions | `references/source-analysis.md` | | Replay readiness, routes, baseline, stack choice, projectization | `references/replay-policy.md` | | QA, failure routing, severity, mismatch signatures | `references/qa-failure-policy.md` | | Three.js shader injection or TSL reconstruction | `references/three-shader-reconstruction.md` | | Unicorn Studio target | `references/unicorn-studio.md` | | shaders.com / TSL target | `references/shaders-com.md` | ## Tool And Artifact Policy Tools are replaceable capabilities, not prerequisites. First record the available capability profile: ```text navigate, runtime-eval, preload-script, network-metadata, network-body, source-map, canvas-screenshot, interaction, frame-capture-webgl, frame-capture-webgpu, local-run, multi-frame-compare ``` Use `scripts/fetch-rendered-dom.mjs` only as an optional inventory helper when Playwright is already available. Use `scripts/scan-bundle.sh` only on target-bound bundle slices or a precise `nextProbe`. Script output is hypothesis evidence. It never satisfies Surface Attribution, Target Lock, Replay Ready, or QA gates by itself. Use bundled templates as schemas, not free-form notes: - `templates/scout-card.json` - `templates/replay-manifest.json` - `templates/run-state.json` - `templates/qa-report.md` - `templates/known-gaps.md` - `templates/extraction-report.md` ## Platform Adapters Load platform references only after target-bound evidence points there: - Unicorn Studio: `references/unicorn-studio.md` - shaders.com / TSL: `references/shaders-com.md` - Three.js shader injection or TSL: `references/three-shader-reconstruction.md` If no adapter fits, follow generic WebGL, WebGPU, or Canvas2D capture in `references/capture-backends.md`.
Excerpt, first 5,927 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.
Install
Pinned to the audited commit 584a6ee
git clone https://github.com/lixiaolin94/skills git -C skills checkout 584a6ee62212
The author documents no install command, so this uses the repository directly. Our verdict covers commit 584a6ee62212 only.
Works in
The author has not said which agents this skill supports, and we have not tested it in any.
Audit history
Every audit, every source change
- ✓SAFE B 89 / 100
first audit · source
584a6ee62212
Similar skills
obra/superpowers
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions…
obra/superpowers
Use when you have a spec or requirements for a multi-step task, before touching code
obra/superpowers
Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions
Questions about web-shader-extractor
What does the web-shader-extractor skill do?
Is web-shader-extractor safe to install?
What can web-shader-extractor access on my machine?
How current is this page?
Sources
- github.com/lixiaolin94/skills/tree/main/web-shader-extractor — the audited source at commit 584a6ee62212 and every finding aboveObserved · 20 Oct 2026
Spotted something wrong? Report a correction · Methodology
Keep going in your AI
Opens with this page as the source. We add nothing else to the prompt.
- What does the web-shader-extractor skill do?
- Is web-shader-extractor safe to install?
- What can web-shader-extractor access on my machine?