菜单
Discover and identify any technology, framework, or system without prior knowledge. Analyzes files, configurations, dependencies, and usage patterns to understand project technology stack from C source files to Kubernetes manifests.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/diegosouzapw/awesome-omni-skill --skill guid-universal-technology-discovery命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
基于 SOC 职业分类
正在显示 SKILL.md
| name | guid-universal-technology-discovery |
| description | Discover and identify any technology, framework, or system without prior knowledge. Analyzes files, configurations, dependencies, and usage patterns to understand project technology stack from C source files to Kubernetes manifests. |
| model | inherit |
What: Systematically identifies and documents all technologies, frameworks, libraries, and their versions used within a project, from low-level source files to high-level infrastructure manifests.
When: Use this skill when you need to understand the technology stack of a project, especially when:
Context: Crucial for understanding the technical landscape of any software project, regardless of its size or complexity. It applies to diverse environments, including on-premise, cloud-based, containerized, serverless deployments, and multi-language projects.
Package Manager Usage
npm, yarn, pnpm for Node.js; pip, poetry for Python; Maven, Gradle for Java]dependencies, devDependencies, peerDependencies]package-lock.json/yarn.lock]Framework Detection Indicators
package.json scripts like start, build, specific component file extensions like .jsx, .tsx, .vue, .svelte]app.js/server.ts, database connection strings, framework-specific configuration files]Dockerfile, docker-compose.yml, kubernetes/*.yaml, terraform/*.tf]Versioning Strategy
^, tilde ~].nvmrc or package.json, Python version in pyproject.toml]Step 1: Comprehensive File Analysis
Step 2: Technology Inference
Step 3: Validation and Verification
Proprietary and Custom Technologies:
Legacy Technology Analysis:
Mixed Environment Discovery:
Problem: Relying only on package.json or visible dependencies; assuming technologies based on file extensions alone; ignoring configuration files and build scripts; missing indirectly used technologies. Why It Fails: Leads to an inaccurate understanding of the actual runtime environment and potential conflicts. Better Approach: Always perform multi-layer analysis (files, configuration, code) and consider deployment and operational environments.
Problem: Confusing installed technologies with actually used ones; missing runtime-discovered dependencies; ignoring dynamically loaded technologies or those discovered through configuration. Why It Fails: Provides an incomplete or incorrect view of the active technology stack. Better Approach: Use both static analysis and runtime behavior understanding; always verify technologies are actually used.
Problem: Missing technologies behind reverse proxies or gateways; ignoring external service integrations; overlooking technologies in different repositories; missing technologies discovered through environment variables. Why It Fails: Leads to blind spots in the system's architecture and potential integration failures. Better Approach: Analyze all project areas, not just obvious ones; test technology integrations and dependencies; validate configuration accuracy and completeness.
Problem: The documented technology stack does not reflect the current state of the project. Why It Fails: Causes confusion, incorrect assumptions, and potential security risks from unpatched versions. Better Approach: Automate technology detection during CI/CD or periodically review and update documentation.
The universal technology discovery provides the foundation for comprehensive project analysis by identifying all technologies present, regardless of how they're implemented or integrated. Effective discovery requires comprehensive analysis, rigorous validation, and clear documentation.