Skip to content
Back to skills

Agent Skills Architecture

ASecurity

Foundational "High-Density" standard for token-optimized agent instructions and CLI-based automated activation.

  • 43 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added May 30, 2026
ai-agentsgo

Works with

  • cli

Security analysis

A100/100

Scanned May 30, 2026

npx -y skills add ComeOnOliver/skillshub --skill agent-skills-architecture --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Agent Skills Architecture?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Agent Skills Architecture
[![Security: A β€” Skills Directory](https://www.skillsdirectory.com/api/skills/comeonoliver-agent-skills-architecture/badge)](https://www.skillsdirectory.com/skills/comeonoliver-agent-skills-architecture)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: Agent Skills Architecture
description: Foundational "High-Density" standard for token-optimized agent instructions and CLI-based automated activation.
metadata:
  labels: [architecture, high-density, meta, optimization, cli-integration]
  triggers:
    files: ['.skillsrc', 'metadata.json', 'SKILL.md']
    keywords:
      [
        skill architecture,
        high-density standard,
        modular skills,
        dependency exclusion,
        skill separation,
      ]
---

# Agent Skills Architecture Standard

## **Priority: P0 (CRITICAL)**

The primary goal is **Maximum Information Density** and **Automated Precision**.

## πŸ—οΈ Core Architectural Pillars

### 1. **Separation by Package (Granularity)**

- **Rule**: Separate skills based on specific library/framework dependencies.
- **Goal**: Avoid context pollution. Don't load "Riverpod" instructions into a "BLoC" project.
- **Example**: `flutter/bloc-state-management` vs `flutter/riverpod-state-management`.

### 2. **Presence = Active (Simplified Configuration)**

- **Logic**: If a skill is listed in `.skillsrc`, it is considered active.
- **Standard**: Remove legacy `enabled` flags. Control activation via inclusion/exclusion lists.

### 3. **CLI Detection & Dynamic Exclusion**

- **Mechanism**: The CLI (`ags`) maps `package.json`/`pubspec.yaml` dependencies to skill IDs.
- **Exclusion**: Irrelevant sub-skills are automatically added to the `exclude` list during initialization if their corresponding packages are missing.

### 4. **Progressive Disclosure (Three-Level Loading)**

- **Level 1 (Metadata)**: Triggers activation via high-precision keywords/files.
- **Level 2 (SKILL.md Body)**: Core imperative logic (<100 lines). No conversational fluff.
- **Level 3 (References)**: Detailed examples, complex patterns, scripts. Lazy-loaded on-demand.

## πŸ“¦ ID & Naming Standards

- **Category**: Lowercase letters (e.g., `flutter`, `nestjs`).
- **Skill ID**: Kebab-case, must match the directory name.
- **Registry ID**: Must match the Skill ID for automated CLI detection/exclusion.

## πŸ“‹ High-Density Writing Style

- **Imperative Mood**: Use "Use X", "Avoid Y". No "Please" or "You should".
- **Token Compression**: Skip articles ("the", "a") where possible. Use bullet points > paragraphs.
- **Anti-Patterns**: Avoid conversational intros ("In this skill, we see...").

## πŸ”— Internal References

- [Skill Creator Standard](../../skill-creator/SKILL.md) - Detailed authoring rules.
- [Resource Organization](../../skill-creator/references/resource-organization.md) - Folder structure best practices.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…