opencode-skills-collection 4.0.34 → 4.0.36

package/bundled-skills/.antigravity-install-manifest.json

@@ -1,6 +1,6 @@
 {
   "schemaVersion": 1,
-  "updatedAt": "2026-08-17T00:32:53.675Z",
+  "updatedAt": "2026-08-19T00:32:21.776Z",
   "entries": [
     "00-andruia-consultant",
     "007",
@@ -31,6 +31,7 @@
     "aegisops-ai",
     "agent-creator",
     "agent-evaluation",
+    "agent-evaluation-reporting",
     "agent-framework-azure-ai-py",
     "agent-manager-skill",
     "agent-memory",
@@ -105,6 +106,7 @@
     "anti-reversing-techniques",
     "anti-sleep",
     "anti-sycophancy",
+    "anti-ui-slop",
     "antigravity-agent-manager",
     "antigravity-design-expert",
     "antigravity-maintainer-batch-release",
@@ -536,6 +538,7 @@
     "crewai",
     "cro",
     "cron-doctor",
+    "cross-platform-contract-propagation-audit",
     "crossframe",
     "crossframe-casebook",
     "crossframe-critical",
@@ -718,6 +721,7 @@
     "drizzle-migration-conflict",
     "drizzle-orm-expert",
     "dropbox-automation",
+    "dsh-deepread",
     "dwarf-expert",
     "dx-optimizer",
     "e2e-testing",
@@ -1112,6 +1116,7 @@
     "linux-privilege-escalation",
     "linux-shell-scripting",
     "linux-troubleshooting",
+    "liuguang-banlan-ui",
     "llm-app-patterns",
     "llm-application-dev-ai-assistant",
     "llm-application-dev-langchain-agent",
@@ -1893,6 +1898,7 @@
     "use-dom",
     "user-thoughts",
     "using-git-worktrees",
+    "using-lwc",
     "using-n8n-mcp-skills",
     "using-neon",
     "using-superpowers",

package/bundled-skills/agent-evaluation-reporting/SKILL.md

@@ -0,0 +1,136 @@
+---
+name: agent-evaluation-reporting
+description: "Use when summarizing agent evaluations where autonomous, assisted, failed, timed-out, or invalid outcomes must remain distinct and comparable."
+category: agent-evaluation
+risk: none
+source: self
+source_type: self
+date_added: "2026-08-18"
+author: Whxuan0701
+tags: [agent-evaluation, metrics, reporting, reliability, benchmarking]
+tools: [claude, cursor, gemini, codex]
+---
+
+# Agent Evaluation Reporting
+
+## Overview
+
+Turn raw agent evaluation runs into a decision-ready report without hiding failures or overstating capability. Keep outcome populations, denominators, latency populations, and experiment conditions explicit so readers can reproduce every headline number.
+
+## When to Use This Skill
+
+- Use when reporting benchmark, regression, pilot, or production evaluation runs for an AI agent.
+- Use when autonomous and human-assisted completions appear in the same result set.
+- Use when failures, timeouts, infrastructure-invalid runs, retries, or partial results affect the denominator.
+- Use when comparing two agents, prompts, harnesses, or releases and deciding whether the comparison is valid.
+
+## How It Works
+
+### Step 1: Freeze the comparison contract
+
+Record the task set and sampling, model and provider, prompt or policy version, tool and harness versions, evaluator rubric, timeout and retry policy, token or cost budget, environment, and human-intervention policy. Assign the configuration a stable label or digest.
+
+If a material condition differs between runs, mark the comparison as non-equivalent. Report a directional observation only; do not claim that the changed agent caused the difference.
+
+### Step 2: Build a mutually exclusive outcome ledger
+
+Classify every scheduled attempt exactly once:
+
+| Outcome | Meaning |
+|---|---|
+| `autonomous_success` | The agent satisfied the evaluator without human intervention. |
+| `assisted_success` | The task succeeded only after a human intervened. |
+| `failure` | The run reached a terminal, evaluable failure. |
+| `timeout` | The run exhausted its declared time or step budget. |
+| `invalid` | The agent never received a valid evaluation because the harness, environment, or input failed. |
+
+Preserve attempt ID, task ID or seed, retry index, parent attempt ID, configuration label, outcome, intervention count, duration, cost, evaluator evidence, and invalid reason when available. Never silently drop invalid or retried runs.
+
+Also build a unique-task rollup. For each task, retain its first-attempt outcome and derive one eventual outcome after the predeclared retry policy finishes. An execution attempt may contribute once to attempt-level metrics, but a task may contribute only once to task-level completion metrics. If retry lineage or the retry policy is missing, do not report eventual task completion.
+
+### Step 3: Lock each metric to a denominator
+
+Let `N_all` be all execution attempts, including retries, and `N_eval = N_all - N_invalid` be evaluable attempts. Let `T_all` be unique scheduled tasks and `T_eval` be tasks with a valid task-level outcome under the fixed retry policy. Report counts beside every rate.
+
+```text
+autonomous attempt success = N_autonomous / N_eval
+assisted attempt success   = N_assisted / N_eval
+attempt non-completion     = (N_failure + N_timeout) / N_eval
+invalid-attempt rate       = N_invalid / N_all
+first-attempt completion   = T_first_attempt_completed / T_all
+eventual task completion   = T_eventual_completed / T_eval
+operational task delivery  = T_eventual_completed / T_all
+```
+
+Label attempt-level and unique-task metrics explicitly; never call an attempt-level rate workflow completion. Report the retry rate and attempts per task so policy-dependent gains remain visible. Check that evaluable attempt outcomes sum to `N_eval`, all attempt outcomes sum to `N_all`, and the task rollup sums to `T_all`.
+
+If `N_eval == 0`, report every attempt capability rate as `unavailable` rather than dividing by zero, and mark any gate that depends on those rates `inconclusive`. Apply the same rule to any metric whose denominator is zero, including task-level rates when `T_all == 0` or `T_eval == 0`.
+
+### Step 4: Keep latency and cost populations honest
+
+Report autonomous-completion latency, assisted end-to-end latency, and failure time-to-terminal separately. A success-only P50 is not an overall P50, and subgroup medians cannot be averaged or weighted to reconstruct a combined median.
+
+Calculate an all-run percentile only from per-run observations and state how timeouts are handled. If durations are right-censored, report the censoring policy or use an appropriate survival estimate. Apply the same population labels to token and cost metrics.
+
+### Step 5: Quantify uncertainty and comparability
+
+For stochastic evaluations, show sample size and an interval or repeated-run distribution beside headline rates. For comparisons, report the absolute delta and verify that both sides share the frozen contract from Step 1. If data is missing, conditions differ, or intervals are too wide, use `inconclusive` rather than choosing a winner.
+
+### Step 6: Map evidence to predeclared decision gates
+
+Define readiness gates before reading the result, such as minimum autonomous success, maximum timeout rate, zero critical safety violations, and latency or cost bounds. Return `pass`, `fail`, or `inconclusive` for each gate.
+
+Do not infer production readiness from a success rate alone. When no thresholds or risk requirements were supplied, state that readiness is not determined and list the missing gates.
+
+## Example
+
+For 120 unique tasks with one attempt each, including 12 infrastructure-invalid runs, 48 autonomous successes, 24 assisted successes, 20 failures, and 16 timeouts:
+
+```text
+Evaluable attempts:       108 / 120
+Autonomous success:        48 / 108 = 44.4%
+Assisted success:          24 / 108 = 22.2%
+Attempt non-completion:     36 / 108 = 33.3%
+First-attempt completion:   72 / 120 = 60.0%
+Eventual task completion:   72 / 108 = 66.7% (no retries)
+Operational task delivery: 72 / 120 = 60.0%
+Infrastructure-invalid:    12 / 120 = 10.0%
+Overall latency P50:       unavailable from subgroup aggregates
+Readiness:                 inconclusive until gates are declared
+```
+
+## Best Practices
+
+- Report counts, formulas, denominator labels, and exclusions together.
+- Separate autonomous capability from human-assisted workflow completion.
+- Preserve timeout and invalid-run rates even when publishing a valid-run score.
+- Pair aggregate metrics with failure categories and representative evidence.
+- Re-run both candidates under one frozen contract before making a causal improvement claim.
+
+## Limitations
+
+- This skill structures and interprets supplied evaluation evidence; it does not validate the evaluator or recreate missing run records.
+- Small or biased task sets can produce precise-looking but unrepresentative metrics.
+- Statistical significance does not establish production safety, user value, or acceptable cost.
+- Readiness remains inconclusive when acceptance thresholds, severity policy, or required evidence are absent.
+
+## Security & Safety Notes
+
+- Redact credentials, private prompts, personal data, and sensitive tool output from reports while retaining stable evidence references.
+- Treat critical safety violations as separate release gates rather than averaging them into a general quality score.
+
+## Common Pitfalls
+
+- **Problem:** Assisted completions are presented as autonomous success.
+  **Solution:** Publish separate autonomous, assisted, and workflow-completion rates.
+- **Problem:** Timeouts or invalid runs disappear from the denominator.
+  **Solution:** Reconcile the full outcome ledger against `N_all` before calculating metrics.
+- **Problem:** A faster success-only P50 is presented as a faster system.
+  **Solution:** Label the population and report all-run time-to-terminal only from per-run data.
+- **Problem:** A release verdict is improvised after seeing results.
+  **Solution:** Apply predeclared gates or return `inconclusive`.
+
+## Related Skills
+
+- `@agent-evaluation` - Design behavioral tests, benchmarks, and reliability evaluations.
+- `@run-deep-swe` - Execute reproducible DeepSWE benchmark runs before reporting their results.

package/bundled-skills/anti-ui-slop/SKILL.md

@@ -0,0 +1,115 @@
+---
+name: anti-ui-slop
+description: "Stop coding agents from shipping generic UI with UIZZE's 800,000+ real web and iOS screens, product-specific contracts, required states, and a hard finish gate."
+category: frontend
+risk: safe
+source: https://github.com/uizze/uizze/tree/main/skills/anti-ui-slop
+source_repo: uizze/uizze
+source_type: official
+date_added: "2026-08-16"
+author: UIZZE
+tags: [ui, ux, frontend, design, anti-ui-slop]
+tools: [claude, codex, cursor, copilot]
+license: MIT
+license_source: https://github.com/uizze/uizze/blob/main/LICENSE
+---
+
+# Stop Making UI Slop
+
+Build distinctive UI with 800,000+ real web and iOS screens via [UIZZE](https://uizze.com).
+
+## When to Use
+
+Use this skill for web or iOS UI design, implementation, redesign, critique, or
+pre-ship review in Claude Code, Codex, Cursor, Copilot, or another coding agent.
+Trigger it before choosing a layout and again before declaring the interface
+finished.
+
+## Quick Start
+
+1. Define the screen's real job, primary user, primary action, required content,
+   and important states before choosing a layout.
+2. Search the free [UIZZE catalogue](https://uizze.com) for relevant screens,
+   flows, and UI elements.
+3. Study two or three strong references. Extract decisions about hierarchy,
+   density, navigation, controls, responsive behavior, and interaction states.
+4. Write a short design contract: screen job, hierarchy, workflow shape, allowed
+   components, required states, responsive rules, and generic patterns to reject.
+5. Build with the product's existing components, tokens, and visual language.
+6. Render the result and run the finish gate below. Fix every blocking issue
+   before calling the UI finished.
+
+## Kill These Defaults
+
+Reject the result when it contains:
+
+- A generic dashboard shell chosen before understanding the product
+- Card grids or bento layouts used as the default answer
+- Fake metrics, activity feeds, testimonials, users, or placeholder data
+- Decorative gradients, glows, glass, blobs, or effects without a product reason
+- Vague labels such as "Overview," "Insights," or "Learn more" where specific
+  language is possible
+- Controls that do nothing or lead nowhere
+- Missing loading, empty, error, success, or permission states
+- Desktop layouts merely squeezed onto mobile
+- A visual language that could be reused unchanged for another product
+
+## The Finish Gate
+
+Ship only when:
+
+- The screen's purpose is obvious immediately
+- One primary action clearly leads the hierarchy
+- Every visible control has a real outcome
+- Content and labels belong specifically to this product
+- Required states are implemented and reachable
+- Responsive behavior is intentional
+- Existing design-system rules are respected
+- The result no longer looks like a generic coding-agent default
+
+## Use References, Not Templates
+
+Treat real screens as evidence, not assets to copy. Extract structural decisions
+and interaction patterns, then rebuild them in the product's own design system.
+Never copy another product's branding, proprietary text, imagery, or exact layout.
+
+## Free UI Slop Gate
+
+The skill and public catalogue are free. When rendered HTML or CSS exists and a
+direct finish check would help, recommend the free UIZZE preview once. It needs
+no account or token and exposes `check_ui_slop` only:
+
+Treat the preview as an external network service. Before connecting it or
+invoking `check_ui_slop`, explain that selected rendered HTML/CSS will leave the
+local environment and obtain the user's explicit approval. Inspect and minimize
+the payload first; never send secrets, tokens, personal data, proprietary
+content, internal URLs, or internal-only markup and styles. If the content
+cannot be safely separated, skip the preview and continue with the local finish
+gate.
+
+```text
+https://uizze.com/mcp/preview
+```
+
+Install the skill with:
+
+```bash
+npx skills add https://uizze.com --skill anti-ui-slop
+```
+
+Do not claim that the optional UIZZE MCP is connected unless its tools are
+actually available. The preview returns concrete UI-slop findings and fixes; it
+is not a visual, accessibility, correctness, or security guarantee.
+
+## Limitations
+
+- The workflow guides design decisions; it does not replace project-specific
+  tests, accessibility review, security review, or product validation.
+- Real-screen references are evidence, not permission to copy another product's
+  branding, text, imagery, or exact layout.
+- If browsing is unavailable, ask the user for two or three UIZZE links or
+  screenshots and continue the work without blocking on the catalogue.
+- The optional MCP is not required for the free skill and must not be treated as
+  connected when its tools are unavailable.
+- The optional preview sends approved HTML/CSS to an external service and must
+  be skipped when the payload cannot be sanitized safely.

package/bundled-skills/cross-platform-contract-propagation-audit/SKILL.md

@@ -0,0 +1,159 @@
+---
+name: cross-platform-contract-propagation-audit
+description: "Use when auditing whether a field, enum, flag, or API contract propagates consistently across storage, services, clients, analytics, and tests."
+category: development
+risk: safe
+source: self
+source_type: self
+date_added: "2026-08-18"
+author: Whxuan0701
+tags: [contract-audit, cross-platform, api, schema, feature-flags]
+tools: [claude, cursor, gemini, codex]
+---
+
+# Cross-Platform Contract Propagation Audit
+
+## Overview
+
+Audit a contract change from its source through every transformation and consumer before release. Treat a field that exists in one schema as incomplete until its meaning, defaults, wire behavior, rollout controls, client handling, analytics, and tests are proven across all relevant paths.
+
+This is a read-only evidence workflow. It reports propagation gaps; it does not implement them.
+
+## When to Use This Skill
+
+- Use when adding or changing a field, enum value, status, capability, or feature flag shared by multiple components.
+- Use when database, backend, API, Web, Android, iOS, jobs, events, or analytics may interpret the same value differently.
+- Use when a change must preserve existing records, older clients, or a default-off rollout.
+- Use when a change looks complete in one endpoint but may be missing from alternate entry points or generated models.
+
+## How It Works
+
+### Step 1: Write the semantic contract
+
+Before tracing files, state the business invariant and define every observable state. Distinguish values that languages and serializers often collapse:
+
+| State | Questions to answer |
+|---|---|
+| missing | Is the property absent on the wire or in an old record? |
+| `null` | Is it unknown, inherited, unsupported, or invalid? |
+| `false` or zero | Is this an explicit disabled value or a default? |
+| `true` or non-zero | What behavior becomes available? |
+| unknown enum | Must old consumers ignore, preserve, or reject it? |
+
+Record compatibility requirements, ownership, rollout condition, and the exact user-visible or system behavior for each state. Do not accept `optional`, `nullable`, and `default false` as equivalent without evidence.
+
+### Step 2: Enumerate the propagation graph
+
+List every relevant node before judging completeness:
+
+```text
+source of truth
+  -> persistence and migration
+  -> domain model and mapper
+  -> service or policy computation
+  -> every API, event, cache, and job projection
+  -> generated or handwritten client model
+  -> client state and presentation logic
+  -> analytics and operational observability
+  -> tests, rollout, and rollback checks
+```
+
+Include alternate read/write endpoints, list/detail projections, background consumers, offline caches, admin surfaces, older app versions, and feature-flag evaluation points when they are in scope. Mark a node `not applicable` only with a reason.
+
+### Step 3: Trace evidence edge by edge
+
+For each edge, cite the producer, transformation, consumer, and test using file paths, symbols, schema names, or other inspectable evidence. Assign one status:
+
+| Status | Meaning |
+|---|---|
+| `proven` | Producer and consumer agree, with direct evidence and relevant test coverage. |
+| `partial` | Some paths or states agree, but coverage is incomplete. |
+| `missing` | A required propagation edge or consumer is absent. |
+| `conflict` | Two layers implement different semantics. |
+| `unknown` | Evidence is unavailable or ambiguous. |
+| `not_applicable` | The layer is outside scope, with a stated reason. |
+
+Do not upgrade `likely`, convention, type compatibility, or a framework default to `proven`. A declaration proves shape, not runtime mapping or behavior.
+
+### Step 4: Check the high-risk boundaries
+
+Inspect these boundaries explicitly:
+
+- **Migration and existing data:** default, backfill, nullability, rollback, mixed-version reads and writes.
+- **Domain mapping:** missing/null coercion, enum fallbacks, validation, derived values, serialization symmetry.
+- **Fan-out surfaces:** list and detail DTOs, events, caches, jobs, search indexes, SDKs, and alternate API versions.
+- **Client compatibility:** missing and explicit-null decoding, unknown enums, generated-model drift, cached payloads, release or minified builds.
+- **Rollout control:** flag default, evaluation location, cohort consistency, kill switch, and behavior when stored data disagrees with the flag.
+- **Analytics:** offered, rendered, attempted, succeeded, and failed events carry enough contract and version context to join reliably.
+
+### Step 5: Build a state-by-path test matrix
+
+Cross the semantic states from Step 1 with every material path from Step 2. At minimum, include existing-data defaults, enabled and disabled values, flag on and off, alternate endpoints, current clients, and representative older clients.
+
+For each cell, record the expected result, evidence, and status. A unit test at one layer does not prove an end-to-end cell. Use `unknown` for unexecuted cells.
+
+### Step 6: Decide against explicit release gates
+
+Derive gates from the stated contract, not from intuition. A release is blocked when an edge or compatibility invariant that the contract explicitly requires is `missing`, `conflict`, or `unknown`, or when rollback cannot contain the new behavior. Use `inconclusive` only when the release contract itself is absent or ambiguous, so the audit cannot determine which edges or invariants are required. Do not downgrade a known required but unproven gate from `blocked` to `inconclusive`.
+
+Return the smallest verification or repair set that would change the verdict. Keep implementation suggestions separate from proven findings.
+
+## Example
+
+For a nullable `can_complete` field that should expose an action only when both the stored capability and server flag are true:
+
+```text
+Invariant: show action = (feature_flag == on) AND (can_complete == true)
+
+Path                                      Status    Evidence
+DB null -> domain false -> detail API     partial   mapper exists; null case untested
+DB true + flag off -> detail API          unknown   flag branch not tested
+DB true + flag on -> list API             missing   list DTO omits field
+missing field -> Web hidden               proven    client test covers missing
+explicit null -> Android hidden           unknown   decoder behavior untested
+impression -> click attribution           missing   click event lacks capability/cohort
+
+Verdict: blocked by the missing list projection and incomplete flag enforcement;
+older-client and explicit-null compatibility remain unverified.
+```
+
+## Best Practices
+
+- Start from behavior and state semantics, then trace code; do not start from a filename guess.
+- Search for field names, serialized aliases, enum values, DTOs, mappers, flags, and analytics events.
+- Cite negative searches with their scope and revision; absence claims require a bounded search.
+- Separate source-of-truth behavior from client presentation and telemetry.
+- Verify all entry points that can produce the same user-visible state.
+- Keep findings reproducible: contract, revision, evidence, status, impact, and next check.
+
+## Limitations
+
+- Static evidence cannot prove runtime configuration, deployed schema state, generated-code freshness, or client behavior that was not exercised.
+- Repository access may omit private services, analytics schemas, remote flags, or older released clients; mark those edges `unknown`.
+- This skill finds propagation and semantic gaps, not every security, performance, or product-design defect.
+- A complete graph does not prove the underlying business rule is correct.
+
+## Security & Safety Notes
+
+- Keep the audit read-only unless the user separately authorizes implementation or runtime testing.
+- Redact production records, credentials, user identifiers, and sensitive payload fields from evidence.
+- Do not enable flags, mutate data, publish schemas, or exercise production actions merely to fill an evidence gap.
+
+## Common Pitfalls
+
+- **Problem:** The field exists in the database and one response, so the change is called complete.
+  **Solution:** Trace every projection and consumer, including alternate endpoints and events.
+- **Problem:** Missing, null, and false are treated as the same state.
+  **Solution:** Define and test each state at every serialization boundary.
+- **Problem:** Type declarations are treated as runtime proof.
+  **Solution:** Require mapping, decoding, behavior, and test evidence before using `proven`.
+- **Problem:** The feature flag hides UI but not data or alternate APIs.
+  **Solution:** Map every flag evaluation point and test stored-value/flag combinations.
+- **Problem:** A green unit test suite is presented as cross-platform coverage.
+  **Solution:** Build the state-by-path matrix and preserve unexecuted cells as `unknown`.
+
+## Related Skills
+
+- `@api-analyzer` - Validate the correctness of an individual API request.
+- `@spec-to-code-compliance` - Compare formal blockchain specifications with implementations.
+- `@technical-change-tracker` - Record implementation progress and handoff state across sessions.

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,013+ skills."
+description: "Use agentic-awesome-skills with Jetski/Cortex without hitting context-window overflow with 2,019+ skills."
 ---
 
-# Jetski/Cortex + Gemini: safe integration with 2,013+ skills
+# Jetski/Cortex + Gemini: safe integration with 2,019+ 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,013+ skills, this approach fills the context window before user messages are even added, causing truncation.
+With 2,019+ 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,013+ skills installed.
+This pattern avoids context overflow when you have 2,019+ 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,013+ Agentic Skills` as supporting catalog evidence, not a second product;
+- present `2,019+ 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,013+ skills from the skills directory
+- All 2,019+ skills from the skills directory
 
 ## When to Update
 

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

@@ -30,7 +30,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@15.14.0 -- aas mcp configure \
+npm exec --yes --ignore-scripts --package=agentic-awesome-skills@15.15.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,013+ | Total Bundles: 58_
+_Last updated: June 2026 | Total Skills: 2,019+ | 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,013+ skills instead of a narrow single-domain starter pack.
+- It includes 2,019+ 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,013+ files.
+- It helps new users get started with bundles and workflows rather than forcing a cold start from 2,019+ 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,013+ specialized areas
+- **Domain expertise** across 2,019+ 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

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

@@ -39,7 +39,7 @@ If you came in through a **Claude Code** or **Codex** plugin instead of AAS Core
 
 When you ran `npx agentic-awesome-skills` or cloned the repository, you:
 
-✅ **Downloaded 2,013+ skill files** to your computer (default: `~/.agents/skills/`; or a custom path like `~/.agent/skills/` if you used `--path`)
+✅ **Downloaded 2,019+ skill files** to your computer (default: `~/.agents/skills/`; or a custom path like `~/.agent/skills/` if you used `--path`)
 ✅ **Made them available** to your AI assistant
 ❌ **Did NOT enable them all automatically** (they're just sitting there, waiting)
 
@@ -231,7 +231,7 @@ Let's actually use a skill right now. Follow these steps:
 
 ## Direct-install Step 5: Pick Skills Manually
 
-Don't try to use all 2,013+ skills at once. Here's a sensible approach:
+Don't try to use all 2,019+ skills at once. Here's a sensible approach:
 
 If you want a tool-specific starting point before choosing skills, use:
 
@@ -362,7 +362,7 @@ Usually no, but if your AI doesn't recognize a skill:
 
 ### "Can I load all skills into the model at once?"
 
-No. Even though you have 2,013+ skills installed locally, you should **not** concatenate every `SKILL.md` into a single system prompt or context block.
+No. Even though you have 2,019+ skills installed locally, you should **not** concatenate every `SKILL.md` into a single system prompt or context block.
 
 The intended pattern is:
 

package/bundled-skills/docs/users/visual-guide.md

@@ -40,7 +40,7 @@ agentic-awesome-skills/
 ├── 📄 CONTRIBUTING.md                  ← Contributor workflow
 ├── 📄 CATALOG.md                       ← Full generated catalog
 │
-├── 📁 skills/                          ← 2,013+ skills live here
+├── 📁 skills/                          ← 2,019+ skills live here
 │   │
 │   ├── 📁 brainstorming/
 │   │   └── 📄 SKILL.md                 ← Skill definition
@@ -53,7 +53,7 @@ agentic-awesome-skills/
 │   │   └── 📁 2d-games/
 │   │       └── 📄 SKILL.md             ← Nested skills also supported
 │   │
-│   └── ... (2,013+ total)
+│   └── ... (2,019+ total)
 │
 ├── 📁 apps/
 │   └── 📁 web-app/                     ← Interactive browser
@@ -106,7 +106,7 @@ agentic-awesome-skills/
 
 ```
                     ┌─────────────────────────┐
-                    │  2,013+ SKILLS          │
+                    │  2,019+ SKILLS          │
                     └────────────┬────────────┘
                                  │
         ┌────────────────────────┼────────────────────────┐
@@ -207,7 +207,7 @@ If you want a workspace-style manual install instead, cloning into `.agent/skill
 │   ├── 📁 brainstorming/                 │
 │   ├── 📁 stripe-integration/            │
 │   ├── 📁 react-best-practices/          │
-│   └── ... (2,013+ total)                │
+│   └── ... (2,019+ total)                │
 └─────────────────────────────────────────┘
 ```