pair-capability-assess-ai

Name: pair-capability-assess-ai
Availability: InStock
Author: Foomakers

Assess and adopt AI development tools using a resolution cascade approach.

6|Updated Aug 3, 2025

Search Tags:#decision making #tech stack #ai #guidelines #development tools #adoption

Ready to run

npx skills add https://github.com/foomakers/pair --skill pair-capability-assess-ai

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pair-capability-assess-ai
Source: https://github.com/foomakers/pair/tree/main/.claude/skills/pair-capability-assess-ai
Command: npx skills add https://github.com/foomakers/pair --skill pair-capability-assess-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of selecting, adopting, and documenting AI development tools, ensuring alignment with project needs and best practices.

Core Features & Use Cases

Tool Selection: Evaluates and recommends AI assistants, MCP integrations, and AI SDKs based on project requirements and guidelines.
Adoption Integration: Updates the project's tech-stack.md file with chosen AI tools and their configurations.
Decision Logging: Records AI tool adoption decisions as non-architectural decisions (ADLs) for traceability.
Use Case: When starting a new project or integrating new AI capabilities, this Skill helps the team quickly decide on the most suitable AI development tools and ensures these decisions are properly documented and recorded.

Quick Start

Use the pair-capability-assess-ai skill to assess and adopt AI development tools for the project.

Frequently Asked Questions about pair-capability-assess-ai

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

FAQPage Schema

How do I select and adopt AI development tools for my project?▼

To adopt AI development tools, this Skill evaluates AI assistants, MCP integrations, and AI SDKs against project guidelines. It proposes tool choices, updates the tech-stack.md file, and logs decisions as non-architectural decision records.

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

Document AI SDK adoption by updating the tech-stack.md file with chosen tools and configurations. The Skill records these tool choices as non-architectural decision logs to ensure full project traceability.

Can I override AI tool recommendations during the assessment process?▼

Yes, the assessment process handles argument overrides for AI tool recommendations. It evaluates existing adoptions and project context using a resolution cascade, ensuring idempotent workflow execution without duplicating entries.

What is the best way to integrate MCP integrations into an existing project?▼

The best way to integrate MCP integrations is by reading project context and AI development guidelines. This Skill assesses these inputs to propose suitable tool choices and automatically updates the tech-stack.md adoption file.

Does this AI tool adoption process support idempotent workflow execution?▼

Yes, the AI tool adoption process supports idempotent workflow execution. It handles full assessments, existing adoptions, and argument overrides safely, preventing duplicate entries when updating the tech-stack.md file.

When do I need to record non-architectural decisions for AI development tools?▼

You need to record non-architectural decisions when adopting AI assistants or SDKs into your project. This Skill logs these tool choices during the resolution cascade to maintain clear adoption traceability.