sickn33/agentic-awesome-skills

AAS Core is the local, agent-first control plane for complete catalog discovery, agent-owned selection, stack validation, and planning, backed by 2,005+...

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 10 minutes ago
Added to GitGenius on August 31st, 2026
Created on January 14th, 2026
Open Issues & Pull Requests: 1 (+0)
Number of forks: 6,695
Total Stargazers: 45,757 (+1)
Total Subscribers: 316 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 0.0 hours
Mean response time: 6.2 hours
90th percentile: 16.7 hours
Tracked items: 167

How this project is maintained

Around half of the issues opened in the past year never receive a reply. Only 19% of issues opened in the past year have been closed. Three people close 96% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 0
New in 7 days: 4
Closed in 7 days: 6
Avg open age: N/A days
Stale 30+ days: 0
Stale 90+ days: 0

Recent activity

Opened in 7 days: 2
Closed in 7 days: 2
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • bug (61)
  • enhancement (14)

Detailed Description

AAS Core is a local, agent-first control plane for AI coding agents to discover, select, and validate skills from a catalog of agentic capabilities.

The tool addresses the problem of giving coding agents access to a complete, curated skill library while maintaining human control and reproducibility. Rather than ranking or recommending skills, AAS Core lets the agent inspect the full project surface—architecture, behavior, data, integrations, testing, security, deployment—then search and compose its own skill stack. The agent's selection is validated in memory through a read-only compose_stack tool, and can be persisted as an immutable aas-stack.json manifest alongside selection evidence that records the agent's reasoning. The CLI provides validation and planning commands to preview changes before applying them, and a browser-based Workbench allows offline review of stack and plan files without filesystem access.

Developers should adopt this tool if they want their coding agents to have agency in skill selection while maintaining auditability and control. It suits projects where reproducibility and review of agent decisions matter—the persisted manifest and evidence sidecar let teams understand exactly which skills were chosen and why. The tool is designed as a local control plane, not a hosted service; the catalog and Workbench are companion discovery surfaces, but the canonical repository and local MCP are where the actual composition and validation happen. Direct installs, plugins, bundles, and workflows remain available as distribution and compatibility layers around the core.

Maintainers typically respond to new issues and pull requests within hours. Work in the issue tracker is dominated by bug and enhancement labels.