assess

Analyze codebase AI-readiness with layered contracts, complexity, and documentation integrity.

30|5|Updated Jan 13, 2026
One-click install
npx skills add https://github.com/bjcoombs/ai-native-toolkit --skill assess-bjcoombs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: assess
Source: https://github.com/bjcoombs/ai-native-toolkit/tree/main/skills/assess
Command: npx skills add https://github.com/bjcoombs/ai-native-toolkit --skill assess-bjcoombs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires networkx, grimp, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This skill addresses the challenge of externalizing codebase context for AI contributors by identifying structural complexity, documentation staleness, and architectural risks that prevent agents from acting like tenured engineers.

Core Features & Use Cases

  • Layered Contract Assessment: Scores a repository across nine layers of AI-readiness, from navigability to feedback loops.
  • Complexity Hotspot Visualization: Generates SVG treemaps where size represents lines of code, hue represents cyclomatic complexity, and saturation represents git churn.
  • Doc Navigability Analysis: Maps documentation connectivity and identifies lying maps where documentation is stale relative to churning code.

Quick Start

Trigger the assess skill by typing /assess in your chat to generate a full AI-readiness report and complexity heatmap for the current repository.

Frequently Asked Questions about assess

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

FAQPage Schema
How do I audit my codebase for AI-readiness and complexity?

Deterministic scans of repository structure, git churn, and link graphs identify structural complexity and maintenance risks, generating an AI-readiness report and complexity heatmap to guide refactoring.

What is a layered contract assessment for repository AI-readiness?

Layered contract assessment scores a repository across nine layers of AI-readiness, ranging from navigability to feedback loops, evaluating how well externalized context enables AI agents to navigate the codebase.

How can I visualize cyclomatic complexity and git churn hotspots?

Generate SVG treemaps where size represents lines of code, hue represents cyclomatic complexity, and saturation represents git churn to pinpoint high-risk maintenance areas and guide refactoring.

How do I detect stale documentation in a churning codebase?

Map documentation connectivity and link graphs to identify lying maps where documentation is stale relative to churning code, exposing doc navigability issues that hinder AI agent contributors.

Does the codebase analysis require networkx or grimp dependencies?

Yes, codebase analysis requires networkx and grimp dependencies to map documentation connectivity and build link graphs for deterministic scans of repository structure and dependency relationships.