Skylv Test Writer

v1.0.0

Auto-generates unit tests and integration tests from source code. Supports Jest, Pytest, Mocha. Triggers: write tests, generate tests, unit test, test covera...

0· 111·0 current·1 all-time

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for sky-lv/skylv-test-writer.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Skylv Test Writer" (sky-lv/skylv-test-writer) from ClawHub.
Skill page: https://clawhub.ai/sky-lv/skylv-test-writer
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install skylv-test-writer

ClawHub CLI

Package manager switcher

npx clawhub@latest install skylv-test-writer
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description (auto-generate tests for Jest/Pytest/Mocha) match the instructions (detect framework, parse source, generate/write test files). No unrelated binaries, env vars, or config paths are requested.
Instruction Scope
Instructions explicitly tell the agent to read project files (package.json, pyproject.toml, source files) and write test files — this is appropriate for generating tests. Note: 'read source files' is necessarily broad; if your repository contains secrets, the skill (when invoked) will have access to them via the agent's workspace. The SKILL.md does not instruct any exfiltration or external network calls.
Install Mechanism
No install spec or code is included (instruction-only), so nothing will be downloaded or written to disk by an installer step. Lowest install risk.
Credentials
No environment variables, credentials, or config paths are requested. The requested access (project files) is proportionate to the stated purpose.
Persistence & Privilege
always is false and the skill does not request persistent/privileged presence. Autonomous invocation is allowed by default (platform behavior) but the skill itself does not request elevated privileges.
Assessment
This skill appears coherent and limited to reading your codebase and writing test files. Before installing, consider: 1) Only run it in a workspace/repo you trust or an isolated copy — it will read repository files and could access secrets present in the repo. 2) Review generated tests before committing; auto-generated tests may mock or call external services if not carefully inspected. 3) No external installers or credentials are required by the skill itself, but verify your agent's runtime permissions so it only accesses the intended project files.

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

latestvk970cwp6e712a0qmsdmwx7177s8586ts
111downloads
0stars
1versions
Updated 1w ago
v1.0.0
MIT-0

Test Writer

Overview

Analyzes source code and auto-generates comprehensive unit and integration tests.

When to Use

  • User asks to "write tests" or "add test coverage"
  • User wants to "test this function"

How It Works

Step 1: Detect test framework

Check: package.json (jest/mocha), pytest.ini, pyproject.toml, conftest.py

Step 2: Parse source

Read source files. Identify: function signatures, parameters, return types, error handling, edge cases.

Step 3: Generate test cases

For each function generate: happy path, edge cases (empty/null/zero), error cases, boundary cases.

Step 4: Write test file

JavaScript: tests/filename.test.js or filename.test.js Python: tests/test_filename.py

Templates

Jest

describe('functionName', () => { test('should return expected result', () => { expect(functionName(input)).toBe(expected); }); test('should throw for invalid input', () => { expect(() => functionName(invalid)).toThrow(); }); });

Pytest

def test_function_normal(): assert function_name(input) == expected

def test_function_invalid(): with pytest.raises(ErrorType): function_name(invalid)

Tips

  • Target 80%+ coverage on critical functions
  • Cover all branches and error paths
  • Mock external dependencies (API, filesystem, DB)

Comments

Loading comments...