techstack-identification

Identify a target's technology stack from public signals into a structured report.

3|1|Updated May 26, 2026
One-click install
npx skills add https://github.com/LeoWSY-hashblue/-communitytools-custom --skill techstack-identification-leowsy-hashblue
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: techstack-identification
Source: https://github.com/LeoWSY-hashblue/-communitytools-custom/tree/main/skills/techstack-identification
Command: npx skills add https://github.com/LeoWSY-hashblue/-communitytools-custom --skill techstack-identification-leowsy-hashblue

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify a target's technology stack using public signals to speed up assessment and reduce guesswork for tech due diligence.

Core Features & Use Cases

  • OSINT-based tech-stack identification across frontend, backend, infra, security, osint, and correlation signals
  • Evidence aggregation, historical context, and migration tracking for decision making
  • Use cases include validating dependencies, versions, and platform choices from public sources

Quick Start

Provide a company name and an optional domain hint, then run the OSINT workflow to generate a structured tech-stack report.

Frequently Asked Questions about techstack-identification

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

FAQPage Schema
How do I identify a target's technology stack from public signals?

Tech-stack identification aggregates public OSINT signals from code repositories, web archives, job postings, TLS/certificate data, and cloud metadata to discover a target's frontend, backend, and infrastructure technologies. This produces a structured report with confidence scoring for decision making.

What is OSINT-based tech-stack discovery used for?

OSINT-based tech-stack discovery is used for tech due diligence, assessments, and migrations. It validates dependencies, versions, and platform choices from public sources, reducing guesswork by providing evidence-backed, structured JSON or Markdown reports.

Can I track historical technology changes and migrations using public OSINT data?

Yes, tech-stack identification supports migration tracking by aggregating historical context from web archives and public signals. It correlates evidence over time to map a target's shifting infrastructure, security, and backend technology choices.

Do I need a company domain to start discovering a target's tech stack?

You need a company name to start the OSINT workflow, while an optional domain hint improves accuracy. The Skill then automatically scopes frontend, backend, infra, and security signals to generate a multi-domain tech-stack report.

What is the best way to generate evidence-backed tech-stack reports for due diligence?

The best way is aggregating public correlation signals from job postings, TLS data, and cloud metadata into a structured output. This approach produces confidence-scored JSON or Markdown reports suitable for validating platform choices and dependencies.

What limitations exist when discovering a tech stack using public signals?

Tech-stack identification is limited to publicly available signals like code repositories, job postings, and TLS data. It cannot uncover internal, proprietary, or heavily obfuscated infrastructure, making confidence scoring essential for assessing the reliability of each discovered technology.