opencode-skills-collection 4.0.43 → 4.0.44

package/bundled-skills/diagram-generator/SKILL.md

@@ -0,0 +1,199 @@
+---
+name: diagram-generator
+description: "Generate, refine, validate, and render diagrams from natural language, notes, code, schemas, or existing diagram sources: flowcharts, swimlanes, attack-path graphs, data-flow diagrams, architecture, and state machines."
+risk: safe
+source: "https://github.com/zhaoxuya520/reverse-skill"
+source_repo: "zhaoxuya520/reverse-skill"
+source_type: community
+date_added: "2026-08-25"
+license: "MIT"
+license_source: "https://github.com/zhaoxuya520/reverse-skill/blob/main/LICENSE"
+---
+# Diagram Generator
+## When to Use
+
+- Turning textual analysis into Mermaid/Graphviz/PlantUML visuals.
+- Producing attack-path or architecture diagrams for reports.
+
+
+## Purpose
+
+Create clear, editable diagrams from messy or structured inputs. Prefer text-based diagram source first so the result can be reviewed, versioned, and refined. Render to files only when the user asks for an image/PDF or when a downloadable artifact would materially help.
+
+## Default workflow
+
+1. Identify the user's intent, audience, and source material.
+2. Choose the diagram family and language using the decision table below.
+3. Normalize entities, relationships, labels, states, branches, and time/order information before writing diagram code.
+4. Generate concise, readable diagram source.
+5. Validate the syntax mentally and, when creating files, run `scripts/render_diagram.py`.
+6. Return the diagram source plus a short note about assumptions. When files are generated, include links to the output files.
+
+Do not over-ask for clarification. If the request is underspecified, make reasonable assumptions and label them briefly.
+
+## Diagram language decision table
+
+Use Mermaid unless another language is clearly better.
+
+| User wants | Prefer | Why |
+|---|---|---|
+| process flow, decision tree, simple swimlane | Mermaid flowchart | readable and easy to paste into Markdown |
+| sequence of system/user interactions | Mermaid sequenceDiagram or PlantUML sequence | Mermaid for docs; PlantUML for UML formality |
+| lifecycle, state machine, transitions | Mermaid stateDiagram-v2 or PlantUML state | compact transition syntax |
+| database schema, entities, relationships | Mermaid erDiagram | portable ER notation |
+| class/interface/object model | Mermaid classDiagram or PlantUML class | Mermaid for docs; PlantUML for detailed UML |
+| project schedule | Mermaid gantt | concise timeline syntax |
+| hierarchy, ideas, notes | Mermaid mindmap | good default for idea maps |
+| customer/product journey | Mermaid journey | built-in journey notation |
+| git history | Mermaid gitGraph | built-in git notation |
+| dependency graph, package graph, large network | Graphviz DOT | better layout engines for dense graphs |
+| architecture with layers, clusters, boundaries | Mermaid flowchart with subgraphs, Graphviz clusters, or PlantUML C4-style | choose based on requested fidelity |
+| weighted flow/sankey-like relationship | Mermaid sankey-beta when supported, otherwise SVG or Graphviz | Mermaid support may vary by renderer |
+| custom visual where source languages fit poorly | SVG | precise control over layout and styling |
+
+## Output policy
+
+- Always provide editable source unless the user explicitly asks only for an image.
+- Default to a single best diagram. Offer alternatives only when genuinely useful.
+- Prefer stable, simple syntax over fancy features that may not render in older Mermaid/PlantUML versions.
+- Use short labels. Split long text into notes outside the diagram when needed.
+- Avoid ambiguous node IDs. Use ASCII IDs and human-readable labels.
+- Preserve user terminology, but standardize capitalization within a diagram.
+- For technical diagrams, include boundaries such as client, service, database, queue, external API, and operator/user when they are implied.
+- For business-process diagrams, distinguish happy path, decision points, failures, retries, and manual steps when present.
+- For diagrams created from uncertain text, include an `Assumptions` section after the code.
+
+## Mermaid generation rules
+
+Consult `references/diagram-patterns.md` for compact templates.
+
+General Mermaid rules:
+- Start with the correct diagram directive, for example `flowchart TD`, `sequenceDiagram`, `erDiagram`, `gantt`, `mindmap`, or `journey`.
+- For flowcharts, use `flowchart TD` unless the user asks for left-to-right; use `flowchart LR` for architecture and pipelines.
+- Use subgraphs for swimlanes or architecture layers. Name subgraphs with readable labels.
+- Keep node IDs stable and ASCII-only, for example `ingest_service[Ingest Service]`.
+- Quote labels that contain punctuation likely to confuse the parser.
+- Use decision diamonds for branching: `decision{Condition?}`.
+- Use consistent edge labels: `-- yes -->`, `-- no -->`, `-. async .->`, or `== critical ==>` only when meaningful.
+- In sequence diagrams, declare participants before messages. Use `actor` for humans and `participant` for systems.
+- Use `alt/else/end`, `opt/end`, `loop/end`, and `par/and/end` blocks for conditional, optional, repeated, and parallel flows.
+
+## Graphviz DOT generation rules
+
+Use Graphviz for large, dense, or layout-sensitive relationship diagrams.
+
+- Prefer `digraph G` for directed relationships and `graph G` for undirected networks.
+- Set layout-friendly graph attributes at the top: `rankdir=LR`, `nodesep`, `ranksep`, and `splines=true` when helpful.
+- Use `subgraph cluster_name` for boundaries and subsystems.
+- Use plain labels and restrained styling.
+- Use edge labels only when they add meaning.
+- For many nodes, group by domain with clusters and avoid crossing-heavy all-to-all edges.
+
+## PlantUML generation rules
+
+Use PlantUML when the user asks for UML or needs formal UML notation.
+
+- Wrap diagrams with `@startuml` and `@enduml`.
+- Use `actor`, `participant`, `database`, `queue`, `collections`, or `component` stereotypes when useful.
+- Use `package`, `rectangle`, or `node` for architecture boundaries.
+- For class diagrams, include only important fields/methods unless the user asks for exhaustive detail.
+- For activity diagrams, use clear start/end markers and explicit branch labels.
+
+## SVG generation rules
+
+Use SVG only when text diagram languages cannot express the requested visual reliably.
+
+- Keep SVG simple, accessible, and editable.
+- Include `<title>` and meaningful text labels.
+- Prefer rectangles, lines, arrows, and groups over complex paths.
+- Do not embed external fonts or remote images.
+
+## Rendering files
+
+When the user asks for PNG/SVG/PDF, create a source file and run:
+
+```bash
+python "<SKILL_ROOT>/diagram-generator/scripts/render_diagram.py" input.mmd --format svg --out output.svg
+python "<SKILL_ROOT>/diagram-generator/scripts/render_diagram.py" input.dot --format png --out output.png
+python "<SKILL_ROOT>/diagram-generator/scripts/render_diagram.py" input.puml --format svg --out output.svg
+```
+
+> `<SKILL_ROOT>` 是本包 `skills/` 目录的实际路径，AI 应自动检测。
+
+The renderer is intentionally dependency-tolerant. It tries common local tools and reports actionable installation hints if a renderer is unavailable. Do not claim an image was rendered unless the script completed successfully and the output file exists.
+
+## Validation checklist
+
+Before finalizing:
+
+- The diagram type matches the user's task.
+- The source is syntactically plausible for the chosen language.
+- Labels are short enough to fit.
+- Edges and message order reflect the input accurately.
+- Assumptions are called out when the input was incomplete.
+- For generated files, the output exists and opens or has nonzero size.
+
+## Common response template
+
+Use this structure for most diagram answers:
+
+```markdown
+下面是可编辑的 [language] 版本：
+
+```[language]
+[source]
+```
+
+Assumptions:
+- [only if needed]
+
+Rendered file: [link] [only if generated]
+```
+
+For English user requests, respond in English. For Chinese user requests, respond in Chinese unless they ask otherwise.
+
+---
+
+## 按需自举（On-Demand Bootstrap）
+
+### 自动化能力边界
+
+| 工具 | 可自动安装 | 安装方式 | 说明 |
+|------|-----------|---------|------|
+| Mermaid CLI (mmdc) | ✓ | npm install -g @mermaid-js/mermaid-cli | 渲染 Mermaid 为 PNG/SVG |
+| Graphviz (dot) | ✗ | 手动安装 | https://graphviz.org/download/ |
+| PlantUML | ✗ | 需要 Java + plantuml.jar | https://plantuml.com/download |
+| Python (render script) | ✓ | 已在 bootstrap 中 | `scripts/render_diagram.py` 依赖 |
+
+### 说明
+
+本 skill 主要输出文本格式的图表源码（Mermaid/DOT/PlantUML），不一定需要本地渲染工具。只有当用户明确要求生成 PNG/SVG/PDF 文件时才需要对应的渲染器。
+
+如果渲染器不可用，`scripts/render_diagram.py` 会输出安装提示而不是报错。
+
+---
+
+## 路由上下文
+
+**上游入口**: `skills/SKILL.md`（总控）、`routing.md`
+**触发条件**: 用户说"画图"、"流程图"、"架构图"、"攻击路径图"、"时序图"、"Mermaid"、"Graphviz"、"PlantUML"
+**下游出口**:
+- 生成的图表可嵌入 `docs-generator/` 的报告中
+- 攻击路径图可配合 `pentest-tools/` 的渗透报告
+
+**同级关联模块**: `docs-generator/`（报告中嵌入图表）
+
+
+## 任务完成自检（声称完成前 MUST 通过）
+
+- [ ] 我是否执行了工作流中的每一步（而不是只阅读）？
+- [ ] 我是否基于 `tool-index` 使用了真实工具路径？
+- [ ] 我是否产出了可复现证据（命令/脚本/截图/报告）？
+- [ ] 我是否完成并回写了 RULES 要求的 Checklist 项？
+
+## Limitations
+
+- Complex auto-layouts may need manual adjustment in the target tool.
+- Rendering fidelity depends on the available diagram CLI/renderer.
+
+> Adapted from [zhaoxuya520/reverse-skill](https://github.com/zhaoxuya520/reverse-skill) (MIT).

package/bundled-skills/diagram-generator/references/README.md

@@ -0,0 +1,3 @@
+# Diagram Generator Skill
+
+This skill helps AI assistants create editable diagrams in Mermaid, Graphviz DOT, PlantUML, and SVG, and optionally render them with local tools.

package/bundled-skills/diagram-generator/references/diagram-patterns.md

@@ -0,0 +1,254 @@
+# Diagram Patterns
+
+Use these compact patterns when generating diagram source. Prefer adapting the pattern instead of inventing complex syntax.
+
+## Mermaid flowchart
+
+```mermaid
+flowchart TD
+  start([Start]) --> receive[Receive request]
+  receive --> valid{Valid?}
+  valid -- yes --> process[Process request]
+  valid -- no --> fix[Ask for missing info]
+  process --> finish([Finish])
+```
+
+## Mermaid swimlane-style flowchart
+
+```mermaid
+flowchart LR
+  subgraph customer[Customer]
+    c1[Submit order]
+  end
+  subgraph app[Application]
+    a1[Validate order]
+    a2[Create invoice]
+  end
+  subgraph ops[Operations]
+    o1[Review exception]
+  end
+  c1 --> a1
+  a1 -- valid --> a2
+  a1 -- invalid --> o1
+```
+
+## Mermaid architecture
+
+```mermaid
+flowchart LR
+  user[User] --> web[Web App]
+  web --> api[API Service]
+  api --> db[(Database)]
+  api -. async .-> queue[[Queue]]
+  queue --> worker[Worker]
+  worker --> object_store[(Object Store)]
+```
+
+## Mermaid sequence diagram
+
+```mermaid
+sequenceDiagram
+  actor User
+  participant Web
+  participant API
+  database DB
+  User->>Web: Submit request
+  Web->>API: POST /request
+  API->>DB: Save record
+  DB-->>API: OK
+  API-->>Web: 201 Created
+  Web-->>User: Show confirmation
+```
+
+## Mermaid ER diagram
+
+```mermaid
+erDiagram
+  CUSTOMER ||--o{ ORDER : places
+  ORDER ||--|{ ORDER_ITEM : contains
+  PRODUCT ||--o{ ORDER_ITEM : appears_in
+  CUSTOMER {
+    string id PK
+    string email
+  }
+  ORDER {
+    string id PK
+    string customer_id FK
+    datetime created_at
+  }
+```
+
+## Mermaid state diagram
+
+```mermaid
+stateDiagram-v2
+  [*] --> Draft
+  Draft --> Submitted: submit
+  Submitted --> Approved: approve
+  Submitted --> Rejected: reject
+  Approved --> [*]
+  Rejected --> Draft: revise
+```
+
+## Mermaid class diagram
+
+```mermaid
+classDiagram
+  class User {
+    +string id
+    +string email
+    +login()
+  }
+  class Order {
+    +string id
+    +decimal total
+    +submit()
+  }
+  User "1" --> "0..*" Order : places
+```
+
+## Mermaid gantt
+
+```mermaid
+gantt
+  title Delivery Plan
+  dateFormat  YYYY-MM-DD
+  section Discovery
+  Requirements        :a1, 2026-01-01, 5d
+  Design              :after a1, 4d
+  section Build
+  Implementation      :2026-01-10, 10d
+  QA                  :2026-01-22, 5d
+```
+
+## Mermaid mindmap
+
+```mermaid
+mindmap
+  root((Product Launch))
+    Research
+      Customer interviews
+      Market scan
+    Build
+      Prototype
+      QA
+    Go-to-market
+      Pricing
+      Campaign
+```
+
+## Mermaid user journey
+
+```mermaid
+journey
+  title Trial Signup Journey
+  section Discover
+    Visit landing page: 4: User
+    Compare pricing: 3: User
+  section Activate
+    Create account: 5: User
+    Invite teammate: 4: User
+```
+
+## Graphviz dependency graph
+
+```dot
+digraph G {
+  rankdir=LR;
+  node [shape=box, style=rounded];
+  app -> api;
+  api -> auth;
+  api -> db;
+  worker -> queue;
+  worker -> db;
+}
+```
+
+## Graphviz clustered architecture
+
+```dot
+digraph G {
+  rankdir=LR;
+  compound=true;
+  node [shape=box, style=rounded];
+
+  subgraph cluster_client {
+    label="Client";
+    web;
+    mobile;
+  }
+
+  subgraph cluster_platform {
+    label="Platform";
+    api;
+    worker;
+    queue [shape=cylinder];
+    db [shape=cylinder];
+  }
+
+  web -> api;
+  mobile -> api;
+  api -> db;
+  api -> queue;
+  queue -> worker;
+  worker -> db;
+}
+```
+
+## PlantUML sequence
+
+```plantuml
+@startuml
+actor User
+participant Web
+participant API
+database DB
+User -> Web: Submit request
+Web -> API: POST /request
+API -> DB: Save record
+DB --> API: OK
+API --> Web: 201 Created
+Web --> User: Confirmation
+@enduml
+```
+
+## PlantUML component architecture
+
+```plantuml
+@startuml
+actor User
+rectangle "Client" {
+  [Web App]
+}
+rectangle "Backend" {
+  [API Service]
+  queue "Queue"
+  [Worker]
+  database "Database"
+}
+User --> [Web App]
+[Web App] --> [API Service]
+[API Service] --> Database
+[API Service] --> Queue
+Queue --> [Worker]
+[Worker] --> Database
+@enduml
+```
+
+## SVG fallback
+
+```svg
+<svg xmlns="http://www.w3.org/2000/svg" width="900" height="360" viewBox="0 0 900 360" role="img">
+  <title>Simple process diagram</title>
+  <defs>
+    <marker id="arrow" markerWidth="10" markerHeight="10" refX="8" refY="3" orient="auto">
+      <path d="M0,0 L0,6 L9,3 z" />
+    </marker>
+  </defs>
+  <rect x="40" y="120" width="160" height="70" rx="10" fill="white" stroke="black" />
+  <text x="120" y="160" text-anchor="middle">Start</text>
+  <line x1="200" y1="155" x2="320" y2="155" stroke="black" marker-end="url(#arrow)" />
+  <rect x="320" y="120" width="180" height="70" rx="10" fill="white" stroke="black" />
+  <text x="410" y="160" text-anchor="middle">Process</text>
+</svg>
+```

package/bundled-skills/digital-forensics/SKILL.md

@@ -0,0 +1,93 @@
+---
+name: digital-forensics
+description: "Authorized digital forensics: memory dumps, disk timelines, PCAP investigation, artifact triage, and incident-response evidence preservation."
+risk: safe
+source: "https://github.com/zhaoxuya520/reverse-skill"
+source_repo: "zhaoxuya520/reverse-skill"
+source_type: community
+date_added: "2026-08-25"
+license: "MIT"
+license_source: "https://github.com/zhaoxuya520/reverse-skill/blob/main/LICENSE"
+---
+# Digital Forensics & IR Artifacts
+## When to Use
+
+- Investigating a suspected incident with forensic rigor.
+- Building defensible timelines from disk/memory/network artifacts.
+
+
+## 适用场景
+
+- 内存转储分析（Volatility 2/3）
+- 磁盘/ E01 / 落地文件时间线
+- PCAP 溯源与协议还原（可联合 `protocol-reverse/`）
+- 主机伪影：Prefetch、Shimcache、Event Log、浏览器历史
+- 应急响应 IOC 提炼（联合 `malware-analysis/` / `threat-hunting/`）
+
+## 工作流
+
+### 1. 保全
+
+```text
+□ 计算 SHA256；记录时区与采集命令
+□ 工作在副本上；原始只读
+□ chain of custody 备注写入 timeline
+```
+
+### 2. 内存
+
+```bash
+vol -f mem.dmp windows.info
+vol -f mem.dmp windows.pslist
+vol -f mem.dmp windows.netscan
+vol -f mem.dmp windows.cmdline
+```
+
+### 3. 主机伪影
+
+```text
+□ 事件日志：Security / PowerShell / Sysmon
+□ 持久化：Run 键、服务、计划任务、WMI
+□ 执行痕迹：Amcache、Prefetch、BAM
+```
+
+### 4. 网络
+
+```text
+□ tshark 统计会话与 DNS
+□ 导出可疑流 → protocol-reverse 或 malware C2 分析
+```
+
+## 工具链
+
+| 工具 | 用途 |
+|------|------|
+| Volatility 3 | 内存 |
+| Timeline Explorer / Plaso | 超级时间线 |
+| tshark | PCAP |
+| Eric Zimmerman 工具集 | Windows 伪影 |
+| Autopsy / FTK Imager | 磁盘 |
+
+## 参考
+
+- `references/forensics-triage.md`
+- `../malware-analysis/` `../threat-hunting/` `../protocol-reverse/`
+
+## 路由上下文
+
+**上游**: MASTER R25  
+**下游**: 恶意样本深挖 → malware-analysis；规则 → threat-hunting
+
+## 任务完成自检
+
+- [ ] 是否保全哈希与副本策略？
+- [ ] 时间线是否可复核？
+- [ ] IOC 是否脱敏分级？
+- [ ] Checklist？
+
+## Limitations
+
+- Chain-of-custody requirements apply; work on verified copies, never originals.
+- Encrypted or anti-forensic artifacts may be unrecoverable.
+
+> Adapted from [zhaoxuya520/reverse-skill](https://github.com/zhaoxuya520/reverse-skill) (MIT).

package/bundled-skills/digital-forensics/references/forensics-triage.md

@@ -0,0 +1,10 @@
+# 取证分诊顺序
+
+1. 保全与哈希  
+2. 内存急症（进程、网络、注入）  
+3. 持久化与执行痕迹  
+4. 横向与账号异常  
+5. 外联 IOC  
+6. 报告与修复建议  
+
+输出模板字段：Time | Host | Artifact | Finding | Confidence | Evidence path

package/bundled-skills/docs/integrations/jetski-cortex.md

@@ -1,9 +1,9 @@
 ---
 title: Jetski/Cortex + Gemini Integration Guide
-description: "Use agentic-awesome-skills with Jetski/Cortex without hitting context-window overflow with 2,028+ skills."
+description: "Use agentic-awesome-skills with Jetski/Cortex without hitting context-window overflow with 2,074+ skills."
 ---
 
-# Jetski/Cortex + Gemini: safe integration with 2,028+ skills
+# Jetski/Cortex + Gemini: safe integration with 2,074+ skills
 
 > **Custom-host integration:** This guide documents a low-level, direct-manifest lazy loader for Jetski/Cortex and similar hosts. For Codex or Claude Code, the recommended path is [AAS Core](../users/aas-core.md), which provides neutral, deterministic catalog retrieval and validates exact agent-selected IDs through a bounded, read-only MCP server.
 
@@ -25,7 +25,7 @@ Never do:
 - concatenate all `SKILL.md` content into a single system prompt;
 - re-inject the entire library for **every** request.
 
-With 2,028+ skills, this approach fills the context window before user messages are even added, causing truncation.
+With 2,074+ skills, this approach fills the context window before user messages are even added, causing truncation.
 
 ---
 

package/bundled-skills/docs/integrations/jetski-gemini-loader/README.md

@@ -23,7 +23,7 @@ This example shows one way to integrate **agentic-awesome-skills** with a Jetski
 - How to enforce a **maximum number of skills per turn** via `maxSkillsPerTurn`.
 - How to choose whether to **truncate or error** when too many skills are requested via `overflowBehavior`.
 
-This pattern avoids context overflow when you have 2,028+ skills installed.
+This pattern avoids context overflow when you have 2,074+ skills installed.
 
 Manifest contract references:
 

package/bundled-skills/docs/maintainers/repo-growth-seo.md

@@ -29,7 +29,7 @@ Preferred homepage:
 Preferred social preview:
 
 - lead with `AAS Core` and the profile → stack → plan flow;
-- present `2,028+ Agentic Skills` as supporting catalog evidence, not a second product;
+- present `2,074+ Agentic Skills` as supporting catalog evidence, not a second product;
 - mention Codex and Claude as the current Core agent path, with broader host compatibility as distribution support;
 - avoid dense text and tiny logos that disappear in social cards.
 

package/bundled-skills/docs/maintainers/skills-update-guide.md

@@ -72,7 +72,7 @@ The update process refreshes:
 - Canonical skills index (`skills_index.json`)
 - Compatibility mirror (`data/skills_index.json`)
 - Web app skills data (`apps\web-app\public\skills.json`)
-- All 2,028+ skills from the skills directory
+- All 2,074+ skills from the skills directory
 
 ## When to Update
 

package/bundled-skills/docs/sources/sources.md

@@ -20,6 +20,15 @@ If you recognize your work here and it is not properly attributed, please open a
 | `react-patterns`            | [React Docs](https://react.dev/)                                           | CC-BY          | Official patterns.            |
 | **All Official Skills**     | [Anthropic / Google / OpenAI / Microsoft / Supabase / Apify / Vercel Labs] | Proprietary    | Usage encouraged by vendors.  |
 
+## Skills from zhaoxuya520/reverse-skill
+
+The following 43 security skills were adapted from the [reverse-skill](https://github.com/zhaoxuya520/reverse-skill) cybersecurity routing pack (MIT). The GPLv3 `CTF-Sandbox-Orchestrator` sidecar and runtime bootstrap scripts were intentionally not bundled.
+
+| Skill | Original Source | License | Notes |
+| :---- | :-------------- | :------ | :---- |
+| `api-security`, `apk-reverse`, `attack-chain`, `binary-diff`, `browser-extension-reverse`, `case-review`, `cloud-k8s`, `code-audit`, `database-security`, `diagram-generator`, `digital-forensics`, `docs-generator`, `dotnet-reverse`, `edr-bypass-re`, `email-security`, `firmware-pentest`, `ghidra-reverse`, `go-rust-reverse`, `hardware-security`, `ida-reverse`, `identity-federation`, `js-reverse`, `llm-security`, `macos-reverse`, `malware-analysis`, `mobile-reverse`, `ot-ics`, `patch-diff-exploit`, `pentest-tools`, `protocol-reverse`, `pwn-chain`, `radare2`, `radio-sdr`, `reverse-browser-automation`, `reverse-engineering`, `supply-chain-security`, `thick-client`, `threat-hunting`, `threat-intelligence`, `wifi-wireless`, `windows-ad`, `reverse-engineering/dsl-vm-reverse`, `pentest-tools/src-hunter` | [zhaoxuya520/reverse-skill](https://github.com/zhaoxuya520/reverse-skill) | MIT | Reverse engineering, binary analysis, offensive assessment, and threat-intelligence workflows, adapted with English metadata and upstream safety gates. |
+
+
 ## Skills from VoltAgent/awesome-agent-skills
 
 The following skills were added from the curated collection at [VoltAgent/awesome-agent-skills](https://github.com/VoltAgent/awesome-agent-skills):

package/bundled-skills/docs/users/aas-core.md

@@ -31,7 +31,7 @@ AAS MCP does not scan the repository and does not decide which skills are best.
 > **Release boundary:** AAS Core landed after release 14.6.0. Use an exact Core-capable release rather than an unreviewed moving tag.
 
 ```bash
-npm exec --yes --ignore-scripts --package=agentic-awesome-skills@16.1.0 -- aas mcp configure \
+npm exec --yes --ignore-scripts --package=agentic-awesome-skills@16.2.0 -- aas mcp configure \
   --host codex \
   --scope user \
   --config /absolute/path/to/codex/config.toml \

package/bundled-skills/docs/users/bundles.md

@@ -1064,4 +1064,4 @@ Found a skill that should be in a bundle? Or want to create a new bundle? [Open
 
 ---
 
-_Last updated: June 2026 | Total Skills: 2,028+ | Total Bundles: 58_
+_Last updated: June 2026 | Total Skills: 2,074+ | Total Bundles: 58_

package/bundled-skills/docs/users/claude-code-skills.md

@@ -17,7 +17,7 @@ Configure AAS Core for Claude Code, describe the task and constraints, let Claud
 - It lets Claude search the verified local catalog without loading the full library into context.
 - It preserves Claude's exact selection without using metadata as an eligibility gate.
 - It keeps MCP discovery read-only and CLI changes approval-gated.
-- It includes 2,028+ skills instead of a narrow single-domain starter pack.
+- It includes 2,074+ skills instead of a narrow single-domain starter pack.
 - It supports the standard `.claude/skills/` path and the Claude Code plugin marketplace flow.
 - It also ships generated bundle plugins so teams can install focused packs like `Essentials` or `Security Developer` from the marketplace metadata.
 - It includes onboarding docs, bundles, and workflows so new users do not need to guess where to begin.

package/bundled-skills/docs/users/gemini-cli-skills.md

@@ -12,7 +12,7 @@ Install into the Gemini skills path, then ask Gemini to apply one skill at a tim
 
 - It installs directly into the expected Gemini skills path.
 - It includes both core software engineering skills and deeper agent/LLM-oriented skills.
-- It helps new users get started with bundles and workflows rather than forcing a cold start from 2,028+ files.
+- It helps new users get started with bundles and workflows rather than forcing a cold start from 2,074+ files.
 - It is useful whether you want a broad internal skill library or a single repo to test many workflows quickly.
 
 ## Install Gemini CLI Skills

package/bundled-skills/docs/users/kiro-integration.md

@@ -18,7 +18,7 @@ Kiro is AWS's agentic AI IDE that combines:
 
 Kiro's agentic capabilities are enhanced by skills that provide:
 
-- **Domain expertise** across 2,028+ specialized areas
+- **Domain expertise** across 2,074+ specialized areas
 - **Best practices** from Anthropic, OpenAI, Google, Microsoft, and AWS
 - **Workflow automation** for common development tasks
 - **AWS-specific patterns** for serverless, infrastructure, and cloud architecture