assess-ai

Assess AI development tools and record decisions in tech-stack.md.

6|Updated Aug 3, 2025
One-click install
npx skills add https://github.com/foomakers/pair --skill assess-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: assess-ai
Source: https://github.com/foomakers/pair/tree/main/packages/knowledge-hub/dataset/.skills/capability/assess-ai
Command: npx skills add https://github.com/foomakers/pair --skill assess-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps teams select and adopt appropriate AI development tools, ensuring alignment with project needs and existing infrastructure.

Core Features & Use Cases

  • Tool Evaluation: Assesses AI assistants, MCP integrations, and AI SDKs based on project requirements and guidelines.
  • Adoption Integration: Writes or updates the AI section of the tech-stack.md adoption file.
  • Decision Recording: Logs AI tool decisions as non-architectural ADLs.
  • Use Case: A new project needs to integrate AI for code generation and architecture review. This Skill guides the team through evaluating options like Cursor, Copilot, or Claude Code, documenting the chosen tools, and updating the project's technical stack documentation.

Quick Start

Use the assess-ai skill to evaluate and select the primary AI development assistant for the current project.

Frequently Asked Questions about assess-ai

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

FAQPage Schema
How do I choose the right AI development tools for my project?

To choose the right AI development tools, this Skill evaluates AI assistants, MCP integrations, and AI SDKs against project requirements and comprehensive guidelines. It assesses arguments and existing adoption files to select the most appropriate options.

What is the best way to evaluate AI assistants like Cursor or Copilot for a new project?

Evaluating AI assistants like Cursor or Copilot involves assessing them through a resolution cascade of arguments and existing adoption files. This ensures the selected tool aligns with project needs and existing infrastructure guidelines.

How do I document AI tool adoption decisions in my tech stack?

Documenting AI tool adoption decisions involves writing or updating the AI section of the `tech-stack.md` adoption file. The Skill also logs the specific AI tool decisions as non-architectural ADLs for project records.

Can I integrate MCP integrations and AI SDKs into my existing technical stack documentation?

You can integrate MCP integrations and AI SDKs into technical stack documentation by evaluating them against project guidelines and writing the chosen tools directly into the AI section of the `tech-stack.md` adoption file.

Does the AI tool assessment process record decisions as architectural decisions?

The AI tool assessment process does not record decisions as architectural decisions; instead, it logs the chosen AI tools as non-architectural ADLs to differentiate general tool adoption from core architectural changes.