Skills test-scaffolding

📦

test-scaffolding

Name: test-scaffolding
Author: Consiliency

Content revision r1 Safe ⚙️ External commands⚡ Contains scripts📁 Filesystem access

Generate Multi-Language Test Scaffolds

Creating consistent test skeletons across mixed-language repositories takes time. This skill analyzes public symbols and generates framework-specific scaffolds with fixtures, mocks, and TODO markers.

Supports: Claude Codex Code(CC)

🥉 78 Bronze

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request

Review the Skillstore skill "test-scaffolding" from https://skillstore.io/skills/consiliency-test-scaffolding.md and its manifest at https://skillstore.io/api/skills/consiliency-test-scaffolding/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/consiliency-test-scaffolding.md Signed manifest GET /api/skills/consiliency-test-scaffolding/manifest Signed lockfile GET /api/skills/consiliency-test-scaffolding/lockfile

Test it

Using "test-scaffolding". Create pytest scaffolds for the authentication module without overwriting tests.

Expected outcome:

Generated a test file for authenticate, refresh, and invalidate.
Added fixture and TODO stubs.
Reported one generated file and three testable units.

Using "test-scaffolding". Scaffold Go tests for exported functions in the billing package.

Expected outcome:

Created a conventional Go test file beside the source.
Added table-driven test placeholders for exported functions.
Reported the generated file and discovered units.

Using "test-scaffolding". Generate Vitest scaffolds where a test file already exists.

Expected outcome:

Skipped the existing test file and reported the reason without changing its contents.

Security Audit

Safe

v9 • 7/13/2026 Open versioned report

All 40 static alerts are false positives caused by Markdown formatting or ordinary language-specific test syntax. No shell execution, dynamic loading, reconnaissance, path traversal operation, or prompt injection was found; relative import examples only document generated test imports.

Files scanned

1,620

Lines analyzed

Review items

False positives ignored

Risk Factors

No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.

Audited by: codex View Audit History →

Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report

Copy report link

https://skillstore.io/skills/consiliency-test-scaffolding/audits/9?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/consiliency-test-scaffolding/security.svg)](https://skillstore.io/skills/consiliency-test-scaffolding?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/consiliency-test-scaffolding?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/consiliency-test-scaffolding/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/consiliency-test-scaffolding.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

Academic citations (APA · BibTeX · CFF)

APA citation

Consiliency. (2026). test-scaffolding security audit report (audit version 9) [Author version unspecified]. Skillstore. https://skillstore.io/skills/consiliency-test-scaffolding/audits/9

BibTeX citation

@techreport{consiliency-consiliency-test-scaffolding-2026,
  author = {Consiliency},
  title = {test-scaffolding security audit report (audit version 9)},
  institution = {Skillstore},
  year = {2026},
  number = {9},
  url = {https://skillstore.io/skills/consiliency-test-scaffolding/audits/9},
  note = {Author version unspecified}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "test-scaffolding security audit report (audit version 9)"
version: "unspecified"
type: report
authors:
  - name: "Consiliency"
date-released: "2026-07-13"
url: "https://skillstore.io/skills/consiliency-test-scaffolding/audits/9"
identifiers:
  - type: other
    value: "skillstore:consiliency-test-scaffolding:audit:9"
    description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: High

Architecture

Maintainability

Content

Community

Spec Compliance

What You Can Build

Start feature development

Generate a conventional test file before implementing a new Python, TypeScript, Go, Rust, or Dart feature.

Expand test coverage

Create fixtures, mocks, async cases, and error-case stubs for public APIs that need broader coverage.

Standardize repository tests

Apply consistent naming and structure across repositories that use different languages and test frameworks.

Try These Prompts

Scaffold one source file

Scaffold tests for {source_file}. Detect the framework, preserve existing files, and use TODO-style stubs.

Choose framework and location

Generate {framework} scaffolds for {source_files}. Include fixture stubs and mirror the source directory under {output_dir}.

Analyze public APIs

Analyze {source_files} for public APIs, then scaffold tests with {framework}. Report generated files, skipped files, symbols, and unit counts.

Build comprehensive scaffolds

Scaffold tests for {source_files} with {framework} and {naming_convention}. Include fixtures, async cases, error cases, and mocks. Do not overwrite existing tests.

Best Practices

Confirm the detected framework and output directory before generating files.
Keep existing tests protected, and enable the force option only after reviewing target files.
Run the formatter and test command after generation to catch import or syntax issues.

Avoid

Do not treat generated TODO stubs as finished test coverage.
Do not force overwrites when test files contain maintained logic.
Do not rely on regex heuristics for complex macros, decorators, generated exports, or unusual formatting.