Detect
Scan the current project and identify its tech stack, frameworks, tools, and databases. Compare against installed singularskills skills and suggest what's missing.
Prerequisites
None — run anytime in any project.
Process
Scan for tech stack signals:
- Read project root for config files:
package.json → Node.js (check for Next.js, React, Vue, Angular, Express, etc.)
pubspec.yaml → Flutter/Dart
Cargo.toml → Rust
go.mod → Go
requirements.txt / pyproject.toml → Python (check for Django, Flask, FastAPI, etc.)
Gemfile → Ruby (check for Rails, Sinatra, etc.)
Dockerfile / docker-compose.yml → Docker
terraform/ / *.tf → Terraform
.github/workflows/ → GitHub Actions
tsconfig.json → TypeScript
biome.json / .eslintrc → Linting tools
vitest.config / jest.config → Testing frameworks
- Check for databases: Prisma, Drizzle, SQLAlchemy, ActiveRecord, etc.
- Check for cloud providers: AWS (CDK, SAM), GCP, Azure, Vercel, Netlify
- Say whether a shipped stack profile matches, in one line:
matches profile: bun-react-ts when package.json has packageManager starting with bun@ and both next and react among its dependencies; matches profile: rust-gpui when a Cargo workspace member depends on gpui; else matches profile: none (the profiles are the stack files in the pack's references folder; singular-init writes the Stack section)
Inventory existing skills:
- Check the agent's skills folder for installed skills:
.agents/skills/ (Codex, OpenCode, Cursor, GitHub Copilot, Gemini CLI and others) or .claude/skills/ (Claude Code), in the project and in the user's home directory; the pack's skills are the <domain>-<skill> folders there
- Note any other folders there as custom skills
- List what's already available
Identify skill gaps:
- Based on detected tech, suggest skills that would be useful
- Examples: Flutter project → "Dart best practices", "Widget testing", "State management patterns"
- Categorize as: available in marketplace, can be adapted, needs to be created
Write the artifact to .singularskills/detect.md with sections:
- Tech Stack — languages, frameworks, databases, tools detected
- Installed Skills — what singularskills skills are already available
- Recommended Skills — what's missing, organized by: find, adapt, or create
- Suggested Next Steps — specific commands to run
Output
The detection report written to .singularskills/detect.md. Present a summary to the user highlighting:
- Tech stack identified
- Top 3-5 skill recommendations
- Suggested
/singular-find-skill or /singular-create-skill commands to run
1---2name: singular-detect3description: Detect a project's tech stack — languages, frameworks, databases, cloud and tooling — and compare it with installed singularskills skills to recommend skills to find, adapt or create. Use when the user asks which skills would help with their stack, or what skills are missing for the codebase they are working in.4metadata:5 source: https://skillmd.com/skills/bromso/singular-detect6---78# Detect910Scan the current project and identify its tech stack, frameworks, tools, and databases. Compare against installed singularskills skills and suggest what's missing.1112## Prerequisites1314None — run anytime in any project.1516## Process17181. **Scan for tech stack signals:**19 - Read project root for config files:20 - `package.json` → Node.js (check for Next.js, React, Vue, Angular, Express, etc.)21 - `pubspec.yaml` → Flutter/Dart22 - `Cargo.toml` → Rust23 - `go.mod` → Go24 - `requirements.txt` / `pyproject.toml` → Python (check for Django, Flask, FastAPI, etc.)25 - `Gemfile` → Ruby (check for Rails, Sinatra, etc.)26 - `Dockerfile` / `docker-compose.yml` → Docker27 - `terraform/` / `*.tf` → Terraform28 - `.github/workflows/` → GitHub Actions29 - `tsconfig.json` → TypeScript30 - `biome.json` / `.eslintrc` → Linting tools31 - `vitest.config` / `jest.config` → Testing frameworks32 - Check for databases: Prisma, Drizzle, SQLAlchemy, ActiveRecord, etc.33 - Check for cloud providers: AWS (CDK, SAM), GCP, Azure, Vercel, Netlify34 - Say whether a shipped stack profile matches, in one line: `matches profile: bun-react-ts` when `package.json` has `packageManager` starting with `bun@` and both `next` and `react` among its dependencies; `matches profile: rust-gpui` when a Cargo workspace member depends on `gpui`; else `matches profile: none` (the profiles are the stack files in the pack's references folder; `singular-init` writes the Stack section)35362. **Inventory existing skills:**37 - Check the agent's skills folder for installed skills: `.agents/skills/` (Codex, OpenCode, Cursor, GitHub Copilot, Gemini CLI and others) or `.claude/skills/` (Claude Code), in the project and in the user's home directory; the pack's skills are the `<domain>-<skill>` folders there38 - Note any other folders there as custom skills39 - List what's already available40413. **Identify skill gaps:**42 - Based on detected tech, suggest skills that would be useful43 - Examples: Flutter project → "Dart best practices", "Widget testing", "State management patterns"44 - Categorize as: available in marketplace, can be adapted, needs to be created45464. **Write the artifact** to `.singularskills/detect.md` with sections:47 - **Tech Stack** — languages, frameworks, databases, tools detected48 - **Installed Skills** — what singularskills skills are already available49 - **Recommended Skills** — what's missing, organized by: find, adapt, or create50 - **Suggested Next Steps** — specific commands to run5152## Output5354The detection report written to `.singularskills/detect.md`. Present a summary to the user highlighting:55- Tech stack identified56- Top 3-5 skill recommendations57- Suggested `/singular-find-skill` or `/singular-create-skill` commands to run