Is Tech Spec safe and trustworthy?

tashan scores Tech Spec on public evidence — it is currently active. Audit scope: OSV advisories, install-time scripts, build provenance and declared permission surface. We do not review source code or execute the capability.

How do I install Tech Spec?

Drop the skill folder into ~/.claude/skills/ (user scope) or .claude/skills/ (project scope).

Who maintains Tech Spec?

2 GitHub contributors, source: camilooscargbaptista/cto-toolkit.

‹ The Index

Tech Spec

skill

Technical Specification Document: Creates detailed technical specs (RFCs, design docs) for features, systems, and integrations. Use this skill whenever the user wants to write a tech spec, design doc, RFC, technical proposal, system design, or API specification. Also trigger when the user says 'spec out', 'design document', 'technical plan', 'how should we build', 'system design for', or wants to plan the implementation of a feature before coding. Trigger even for informal requests like 'I need to think through how to build X' or 'help me plan the architecture for Y'.

Works with: Claude Code (native) · Cursor, Codex CLI (manual)
native: this artifact type is that client's own format

Category: Design — see all ranked ›

Install (Claude Code):

cp -r tech-spec ~/.claude/skills/

Adoption: 1 repos
Upkeep: 64.0
Freshness: 61.0
Evidence coverage: 84% of the inputs this score can use — the rest are unknown, and the score is discounted for it
Health: active
Contributors: 2
License: MIT

Security audit

Not scanned yet. We audit npm-published capabilities for known advisories, install-time scripts and permission surface; this one has no npm package we can resolve, or has not reached the queue.

source ↗ · skill:camilooscargbaptista/tech-spec

Already running this? npx tashan-cli doctor checks your whole config against the Index — how it works ›

Measured 2026-08-09 · scorer s5 · how · something wrong here?