# Detect Your Project Technology Stack

Technology stacks become difficult to inventory when projects use multiple manifests. This skill inspects local metadata and returns a consistent stack summary.

## Install

```bash
npx skillstore add consiliency/library-detection
```

## Metadata

- Status: approved
- Slug: consiliency-library-detection
- Skillstore revision: r1
- Version status: missing
- Tree hash: 025d428760258b3963bf0fb92aaf13e2ba5d99c24e2c725d39cd8276adf06ad8
- Author: Consiliency
- GitHub username: Consiliency
- License: MIT
- Repository: https://github.com/Consiliency/treesitter-chunker/tree/main/.ai-dev-kit/skills/library-detection
- Ref: 635f69fb8d2f4e6330ba47a4e5a0fb239c04d110
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: filesystem, external\_commands, network
- Quality score: 78
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/consiliency-library-detection
- Manifest: https://skillstore.pages.dev/api/skills/consiliency-library-detection/manifest

## Capabilities

- Guides discovery of supported package manifests and configuration files within a configurable directory depth.
- Extracts production, development, peer, and optional dependency information from common manifest formats.
- Maps known dependencies to frameworks, test tools, build systems, databases, and cloud providers.
- Covers JavaScript, Python, Go, Rust, Dart, Flutter, C, and C\+\+ detection patterns.
- Produces structured summaries in JSON, Markdown, or TOON format.
- Provides read-only command examples for parsing local manifests.

## Use Cases

- Accelerate project onboarding: Create a concise stack inventory before exploring an unfamiliar repository.
- Inventory engineering platforms: Compare frameworks, test tools, build systems, and cloud SDKs across repositories.
- Plan technical documentation: Identify relevant technologies before selecting references and writing setup guidance.

## Prompt Templates

### Summarize the current project

```
Scan the current project for supported manifests. Summarize detected languages, frameworks, test tools, and build systems in Markdown.
```

### Inspect dependencies and services

```
Analyze this repository with development dependencies included. Report database and cloud SDK signals, and cite the manifest supporting each detection.
```

### Compare monorepo packages

```
Scan this monorepo to depth {depth}. Compare stack components by package, then highlight shared tooling and conflicting framework versions.
```

### Verify uncertain detections

```
Audit the detected stack for uncertain classifications. Verify packages against imports and configuration files, distinguish direct from development dependencies, and explain each correction.
```

## Limitations

- Pattern matching can identify installed packages that the project does not actively use.
- Detection is limited to the manifest types and package mappings documented by the skill.
- The skill does not install dependencies, execute builds, or validate runtime behavior.
- Command examples require local tools such as jq, Python, grep, sed, and awk.

## Best Practices

- Run detection from the intended project root and choose a scan depth that includes nested packages.
- Verify detected frameworks against imports and configuration files before using results for automation.
- Review every relevant manifest when a repository contains multiple languages or package managers.

## Anti Patterns

- Do not infer a framework from filenames without checking dependency evidence.
- Do not classify every dependency as a runtime requirement.
- Do not run installers, build scripts, or project executables during stack detection.

## Security Audit

- Audited at: 2026-07-13T16:15:28.848\+00:00
- Summary: All 42 static findings are false positives caused by Markdown syntax, local read-only commands, stderr redirection, and a JSON Schema identifier. No network request, secret access, command injection path, prompt injection, or malicious intent was found.

## Stats

- Views: 420
- Downloads: 6
- Favorites: 0
- Popularity score: 0