tech-stack-scan

Inventories languages, frameworks, libraries, build tooling, CI/CD, and infrastructure with file/line evidence.

3|1|Updated Aug 26, 2026
One-click install
npx skills add https://github.com/zeljkoobrenovic/sokrates-skills --skill tech-stack-scan-zeljkoobrenovic
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tech-stack-scan
Source: https://github.com/zeljkoobrenovic/sokrates-skills/tree/main/skills/scanners/tech-stack-scan
Command: npx skills add https://github.com/zeljkoobrenovic/sokrates-skills --skill tech-stack-scan-zeljkoobrenovic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often lack an accurate picture of what technologies a codebase actually uses — manifests lie, dependencies go unused, and external services hide in config files. This Skill produces an evidence-backed technology inventory of a codebase, with or without a prior Sokrates analysis. ## Core Features & Use Cases - Full-stack inventory: Detects languages, runtimes, frameworks, libraries, build tooling, CI/CD pipelines, infrastructure, databases, external services, and protocols, each cited with file/line evidence. - Gap and risk detection: Flags missing CI, build systems, or lockfiles, plus EOL runtimes, duplicated libraries, risky dependency sourcing, and version fragmentation with severity ratings. - Validated reporting: Writes a structured findings report to _sokrates/reports/ai-insights/tech-stack-scan.json, validates it, and renders an interactive explorer page. - Use Case: Before a migration or audit, ask for a deep tech scan of a repository to get a complete, verifiable list of every framework, datastore, and third-party service the system depends on. ## Quick Start Run a deep tech scan on this repository and tell me what technologies, frameworks, and external services it uses.

Frequently Asked Questions about tech-stack-scan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find out what technologies a codebase uses?

Run a tech stack scan that reads manifests, lockfiles, build files, CI configs, and code-level signals like imports and connection strings. The scan produces a findings report where each technology is backed by file and line evidence.

How to generate a dependency inventory for a tech radar?

The scan groups findings into languages-runtimes, frameworks, libraries, build-tooling, ci-cd, infrastructure, databases-storage, external-services, and protocols-formats. Ecosystem dependency totals are recorded in stats, giving structured input for a tech radar.

Does the tech stack scan work without a Sokrates analysis?

Yes, the scan works with or without an existing _sokrates analysis. When Sokrates data is present it is used for orientation and language metrics, but manifests and code signals are the primary evidence sources.

Can the scan detect unused or risky dependencies?

Yes, it flags declared-but-unused libraries, duplicate-purpose dependencies, git-pinned or vendored sources, wildcard versions, and version fragmentation across workspaces. Each risk gets a severity rating and a recommendation.

Where does the tech stack scan write its results?

Results are written to _sokrates/reports/ai-insights/tech-stack-scan.json following the shared findings format. The report is validated against the schema and then rendered into an interactive HTML explorer page.