10x-stack-assess

Evaluates an existing project's stack against four agent-friendliness quality gates and writes a structured assessment.

Updated May 20, 2026
One-click install
npx skills add https://github.com/ZawilecxD/trAInR --skill 10x-stack-assess-zawilecxd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: 10x-stack-assess
Source: https://github.com/ZawilecxD/trAInR/tree/main/.cursor/skills/10x-stack-assess
Command: npx skills add https://github.com/ZawilecxD/trAInR --skill 10x-stack-assess-zawilecxd

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Teams adopting AI coding agents on existing (brownfield) projects often don't know whether their current stack supports agent workflows well. This Skill inspects the codebase, scores each stack component against four quality gates (typed, convention-based, popular in training data, well-documented), and produces concrete compensation strategies instead of recommending a stack rewrite. ## Core Features & Use Cases - File-driven stack detection: Reads project markers like package.json, pyproject.toml, Cargo.toml, go.mod, and config files to identify language, framework, build tool, test runner, package manager, CI/CD, and deployment target. - Quality gate scoring with evidence: Scores each component against the four agent-friendly criteria, citing the specific file or config that proves each pass or fail. - Ready-to-paste compensation rules: For every failed gate, generates concrete AGENTS.md instruction entries (e.g., routing conventions, type annotation rules) so agents can work effectively despite gaps. - Use Case: A team with an Express.js codebase runs the assessment, learns the stack fails the typed and convention-based gates, and receives paste-ready AGENTS.md rules documenting middleware order and validation patterns before running a health check. ## Quick Start Ask the AI to assess my stack for agent-friendliness in the current project directory.

Frequently Asked Questions about 10x-stack-assess

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

FAQPage Schema
How do I assess if my tech stack is agent-friendly?

Run the assessment in a directory containing project markers like package.json or pyproject.toml. The skill detects your language, framework, build tool, and test runner from on-disk files, then scores each against four quality gates and writes context/foundation/stack-assessment.md.

What are the four agent-friendly quality gates?

The gates are typed (explicit types or configured type checking), convention-based (framework-enforced structure), popular in training data (mainstream within its language family), and well-documented (current, versioned official docs). Each component is scored with evidence from your project files.

Does the stack assessment recommend switching frameworks?

No. The skill never recommends replacing your stack. When a gate fails, it produces compensation strategies: concrete, ready-to-paste rules for AGENTS.md or similar instruction files so AI agents can work effectively despite the gap.

Which languages and project types does stack assessment support?

It detects JS/TS, Python, Rust, Go, Ruby, PHP, .NET, and Dart projects via marker files like package.json, pyproject.toml, Cargo.toml, go.mod, Gemfile, composer.json, csproj, and pubspec.yaml. At least one marker must exist in the working directory.

When should I not run a stack assessment?

Skip it for greenfield projects with no existing code; use a tech stack selector instead. Also skip it if you only want a dependency audit or security scan, which is the job of a health check skill that consumes the assessment output.