ClawHub

Typescript Strict

v1.0.0

Deep TypeScript strictness workflow—incremental enablement, compiler flags, typing boundaries, narrowing, generics, utility types, and safe refactors. Use wh...

⭐ 0· 79·0 current·0 all-time
by@clawkk
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
The name/description (TypeScript strictness workflow) matches the SKILL.md content: incremental strictness stages, compiler flags, IO boundaries, CI guardrails. Nothing requested (no env vars, no installs) contradicts the stated purpose.
ℹ
Instruction Scope
The SKILL.md instructs actions like running `tsc --noEmit`, collecting error counts, and using tools/libraries (zod, io-ts, codegen, ESLint). This is appropriate for the purpose, but the skill does assume developer tooling and access to the repository; it does not explicitly declare those binaries or file access requirements.
✓
Install Mechanism
No install spec and no code files — lowest risk. The skill is instruction-only and does not write or fetch code at install time.
✓
Credentials
No environment variables, credentials, or config paths are requested. The guidance references typical libraries and CI, which is appropriate and proportionate.
✓
Persistence & Privilege
always is false and the skill doesn't request persistent presence or mutate other skills or system-wide settings. Autonomous invocation is allowed by default but not combined with other concerning privileges.
Assessment
This skill is a written workflow for adopting stricter TypeScript settings and appears self-consistent. Before installing or enabling it for autonomous use, confirm the agent will only be given access to the code repository you intend it to analyze (it expects to run tsc/eslint and read source files). Note the SKILL.md assumes developer tooling (Node/tsc/esbuild/ESLint, and optional libs like zod/codegen) but the skill metadata does not declare these as required binaries — make sure those tools exist in the environment. If you allow autonomous invocation, consider scoping repository access and CI secrets so the agent cannot read unrelated projects or sensitive files.

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

latestvk971g9ta7jdg2fy7zg82vybtbs83hrdw

License

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

Comments