lin-tet-master
v1.0.1Use when writing tests, creating test strategies, or building automation frameworks. Invoke for unit tests, integration tests, E2E, coverage analysis, perfor...
⭐ 0· 112·0 current·0 all-time
by@lintqiu
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description describe a testing specialist and all included reference files and SKILL.md content provide testing guidance (unit, integration, E2E, perf, security). There are no unrelated requirements (no env vars, binaries, or installs) that would be disproportionate to the stated purpose.
Instruction Scope
SKILL.md and referenced docs constrain the agent to testing activities (test planning, writing/executing tests, reporting). Example snippets reference local/CI test endpoints (e.g., /api/test/seed, localhost) and test artifacts, but the instructions do not tell the agent to read system secrets, arbitrary host files, or send data to unexpected external servers.
Install Mechanism
No install spec and no code files that would be downloaded or executed. Instruction-only skills are lowest-risk for install mechanism issues.
Credentials
The skill declares no required environment variables, no primary credential, and no config paths. Example code uses test credentials and local endpoints (test@example.com, localhost), which are expected for test guidance.
Persistence & Privilege
always is false and the skill is user-invocable. It does not request permanent presence or system-wide configuration changes. Autonomous invocation is permitted by default on the platform but is not in itself a red flag and is not combined here with other concerns.
Assessment
This skill appears coherent and focused on testing guidance. Before installing or enabling it widely: 1) Ensure any sample endpoints (e.g., /api/test/seed, localhost) are used only against non-production test environments — do not point tests at production or include real credentials. 2) If you let the agent run tests autonomously in your CI or environment, restrict its permissions (CI tokens, databases) to test/sandbox resources. 3) Review any auto-generated test code before executing it (to avoid accidental destructive actions like database wipes). 4) If you want to limit autonomous use, consider disabling model invocation for the skill or restricting when it can run. Overall, the skill is internally consistent but operational caution (test vs prod separation) is recommended.Like a lobster shell, security has layers — review code before you run it.
latestvk979b8yjeqr499gbnncbnjem7s832stb
License
MIT-0
Free to use, modify, and redistribute. No attribution required.