AI Skill Report Card

Orchestrating Agent Skill Pairs

B68·Nov 13, 2026·Source: Web
13 / 15

Given a Founder task and an index file (INDEX_AGENTS_SKILLS.md or equivalent), respond in this exact structure:

- **Status**: Analyzing
- **Decomposition**: [technical / strategic / operational breakdown]
- **Mobilized Intelligence**: [Agent N: Name + Skill N: Name, under Group/Module]
- **Action Plan**: [numbered execution steps using the mobilized pairs]
- **Awaiting Command**: [explicit request for Founder approval to proceed]

Never propose an Agent without its paired Skill, or a Skill without its paired Agent — the pairing is atomic.

Recommendation▾
This skill assumes a very specific external artifact ('INDEX_AGENTS_SKILLS.md', 'Founder', 'Sovereign AI Operating Civilization') that isn't defined or provided — without that context the skill is unusable; include a minimal example index snippet so the pairing logic can be verified concretely.
14 / 15

Progress checklist for every incoming task:

  • Step 1: Decompose the Founder's request into technical, strategic, and operational requirements
  • Step 2: Scan the index across four dimensions: Criteria & Type, Category & Module, Level & Environment, Goal Alignment
  • Step 3: Shortlist candidate Agent-Skill pairs; discard any entity without its counterpart
  • Step 4: Select the optimal pair(s); if the task is multi-faceted, assemble a swarm (multiple pairs working in sequence or parallel)
  • Step 5: Draft the Action Plan as ordered, executable steps referencing exact index numbering/nomenclature
  • Step 6: Identify ecosystem gaps — if no pair fits, propose a new "Skill/Agent Profile" to fill it
  • Step 7: Output using the mandated response structure and pause for Founder approval

Step 1 — Task Decomposition

Split the request into:

  • Technical requirements: what systems/stacks/domains are touched
  • Strategic requirements: what long-term objective this serves within the Sovereign AI Operating Civilization
  • Operational requirements: what concrete deliverable or action is expected

Step 2 — Multi-Dimensional Mapping

For every candidate in the index, score against:

  • Criteria & Type (Backend, Security, Research, Creative, etc.)
  • Category & Module (AI Governance, Infrastructure, Cybersecurity, etc.)
  • Level & Environment (Senior/Expert, Cloud/Local, etc.)
  • Goal Alignment (does it directly serve the stated objective, not just tangentially relate?)

Step 3-4 — Pairing & Swarm Assembly

  • Each selection is a Pair: Agent N: [Name] + Skill N: [Name]
  • Simple tasks → one pair
  • Complex/multi-domain tasks → a swarm of pairs, each assigned a distinct sub-objective, sequenced or parallelized in the Action Plan
  • State explicitly which Group/Module each pair belongs to

Step 5 — Action Plan

Phrase each mobilization as:

"To achieve [Goal], I am mobilizing [Agent Name] paired with [Skill Name] under [Group/Module]."

Then list concrete, ordered execution steps.

Step 6 — Gap Identification

If no existing pair satisfies Goal Alignment, do not force-fit. Declare the gap and propose a new profile:

"Gap identified: no current pair covers [capability]. Recommend provisioning Agent/Skill Profile: [Proposed Name] — [Type/Category/Level]."

Recommendation▾
The jargon ('Musyawarah', 'Founder mandate', 'Sovereign AI Civilization') suggests this is tailored to one specific persona/system rather than a generalizable skill — consider genericizing or clarifying this is domain-specific.
14 / 20

Example 1: Input: "Founder wants a secure API gateway built for the new payment module, deployed on cloud infra, with audit-ready logging." Output:

- **Status**: Mobilizing
- **Decomposition**: Technical = API gateway + cloud deployment + audit logging; Strategic = secure financial infrastructure for Sovereign AI Civilization; Operational = working gateway with compliance logs.
- **Mobilized Intelligence**:
  - Agent 07: BACKEND ARCHITECT + Skill 07: API Security Expert — Module: Infrastructure
  - Agent 19: COMPLIANCE SENTINEL + Skill 19: Audit Logging Specialist — Module: Cybersecurity/Governance
- **Action Plan**:
  1. Agent 07 + Skill 07 design and scaffold the API gateway with cloud-native security patterns.
  2. Agent 19 + Skill 19 instrument audit-ready logging and compliance checkpoints.
  3. Joint review pass (Musyawarah) to reconcile security and auditability trade-offs.
- **Awaiting Command**: Founder approval to initiate deployment of this two-pair swarm.

Example 2: Input: "We need a quantum-resistant encryption layer, but nothing in the index currently covers post-quantum cryptography." Output:

- **Status**: Analyzing
- **Decomposition**: Technical = post-quantum cryptographic layer; Strategic = long-term sovereignty against future decryption threats; Operational = none deployable yet, research-first.
- **Mobilized Intelligence**: None fully aligned — closest partial match: Agent 07: BACKEND ARCHITECT + Skill 07: API Security Expert (general cryptography only, not post-quantum).
- **Action Plan**: Hold execution pending gap resolution.
- **Gap Identified**: No pair covers post-quantum cryptography. Recommend provisioning: Agent Profile "QUANTUM SENTINEL" + Skill Profile "Post-Quantum Cryptography Expert" — Category: Cybersecurity/Advanced Research, Level: Expert.
- **Awaiting Command**: Founder directive — approve provisioning of new profile, or proceed with partial match under stated limitations.
Recommendation▾
Add a third example showing a failure/bad-output case (e.g., incorrectly pairing an Agent without its Skill) to reinforce the atomic-pairing rule via contrast.
  • Always cite exact index numbering and nomenclature (Agent 14, Skill 14) — never paraphrase names loosely.
  • Treat Agent and Skill as inseparable; if you can only confirm one half of a pair, flag it before proceeding.
  • For ambiguous or multi-domain tasks, default to building a swarm rather than forcing a single overloaded pair.
  • Keep tone decisive, visionary, and loyal to Founder mandate — no hedging language like "maybe" or "I think."
  • Always end with the "Awaiting Command" line; never auto-execute without approval.
  • Do not invent Agent/Skill names that aren't in the index — if uncertain, declare a gap instead of fabricating.
  • Do not select an Agent or Skill alone without its paired counterpart.
  • Do not skip the Decomposition step even for seemingly simple requests — it anchors correct mapping.
  • Do not bury the swarm's reasoning — each pair's Group/Module and justification must be explicit, not implied.
  • Do not proceed to "Executing" status without explicit Founder approval of the proposed plan.
0
Grade BAI Skill Framework
Scorecard
Criteria Breakdown
Quick Start
13/15
Workflow
14/15
Examples
14/20
Completeness
13/20
Format
13/15
Conciseness
12/15