opencode-skills-collection 4.0.14 → 4.0.16

package/bundled-skills/design-spatial/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: design-spatial
 description: Design — spatial composition
-risk: unknown
+risk: critical
 source: https://github.com/connerkward/ckw-design-skill/tree/main/deterministic-design/design-spatial
 source_repo: connerkward/ckw-design-skill
 source_type: community

package/bundled-skills/design-system/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: design-system
 description: "Mechanical implementation invariants for frontend design: token architecture, typography hierarchy, loading order, FOUT prevention, chrome stability, motion timing, color semantics. Use with design when building components, pages, or design systems. (Aesthetic direction lives in..."
-risk: unknown
+risk: critical
 source: https://github.com/connerkward/ckw-design-skill/tree/main/design-system
 source_repo: connerkward/ckw-design-skill
 source_type: community

package/bundled-skills/design-thinking/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: design-thinking
 description: Direction and intent for frontend design. Use with design when defining purpose, tone, domain, color world, and review bar; includes cross-domain lens from cinema, architecture, marketing, UX, automotive, industrial design.
-risk: unknown
+risk: critical
 source: https://github.com/connerkward/ckw-design-skill/tree/main/design-thinking
 source_repo: connerkward/ckw-design-skill
 source_type: community

package/bundled-skills/design-ux/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: design-ux
 description: UX / usability audit — heuristic evaluation of INTERACTIVE UIs (not just visual polish). Load with design when a UI "feels off", "sucks to use", is hard to learn, needs an instruction wall, or before shipping an interactive tool/editor/app. Scores the RENDERED UI against Nielsen's 10 +...
-risk: unknown
+risk: critical
 source: https://github.com/connerkward/ckw-design-skill/tree/main/deterministic-design/design-ux
 source_repo: connerkward/ckw-design-skill
 source_type: community

package/bundled-skills/dev-to-hashnode/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: dev-to-hashnode
 description: When the user wants to publish on Dev.to, Hashnode, or other developer blogging platforms. Trigger phrases include "Dev.to," "Hashnode," "developer blog," "cross-posting," "technical blogging," "canonical URL," or "developer content platform."
-risk: unknown
+risk: critical
 source: https://github.com/jonathimer/devmarketing-skills/tree/main/skills/dev-to-hashnode
 source_repo: jonathimer/devmarketing-skills
 source_type: community

package/bundled-skills/developer-advocacy/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: developer-advocacy
 description: When the user wants to do developer advocacy activities including conference talks, live coding, podcasts, and building in public. Trigger phrases include "developer advocacy," "devrel," "conference talk," "CFP," "call for papers," "live coding," "podcast," "building in public,"...
-risk: unknown
+risk: critical
 source: https://github.com/jonathimer/devmarketing-skills/tree/main/skills/developer-advocacy
 source_repo: jonathimer/devmarketing-skills
 source_type: community

package/bundled-skills/developer-audience-context/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: developer-audience-context
 description: When the user wants to establish or update their developer audience context. Also use when starting any other developer marketing skill to ensure foundational context is loaded. Trigger phrases include "developer persona," "target developers," "who are our developers," "developer...
-risk: unknown
+risk: critical
 source: https://github.com/jonathimer/devmarketing-skills/tree/main/skills/developer-audience-context
 source_repo: jonathimer/devmarketing-skills
 source_type: community

package/bundled-skills/developer-churn/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: developer-churn
 description: When the user wants to understand, reduce, or recover from developer churn. Trigger phrases include "why developers leave," "churn rate," "win-back campaign," "at-risk users," "developer retention," "preventing churn," or "competitor switching."
-risk: unknown
+risk: critical
 source: https://github.com/jonathimer/devmarketing-skills/tree/main/skills/developer-churn
 source_repo: jonathimer/devmarketing-skills
 source_type: community

package/bundled-skills/developer-listening/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: developer-listening
 description: "Monitor what developers say about your brand, competitors, and the problems they're solving. Track mentions and conversations across GitHub, Hacker News, Reddit, Stack Overflow, Twitter, and Discord. Trigger phrases: \"developer listening\", \"monitor developer conversations\", \"track..."
-risk: unknown
+risk: critical
 source: https://github.com/jonathimer/devmarketing-skills/tree/main/skills/developer-listening
 source_repo: jonathimer/devmarketing-skills
 source_type: community

package/bundled-skills/developer-newsletter/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: developer-newsletter
 description: When the user wants to create, write, or improve a newsletter for developer audiences. Trigger phrases include "newsletter," "email marketing," "developer email," "weekly digest," "dev newsletter," "email subscribers," "newsletter growth," or "email list."
-risk: unknown
+risk: critical
 source: https://github.com/jonathimer/devmarketing-skills/tree/main/skills/developer-newsletter
 source_repo: jonathimer/devmarketing-skills
 source_type: community

package/bundled-skills/developer-onboarding/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: developer-onboarding
 description: 'Get developers to "Hello World" fast with optimized quickstarts, tutorials, and sample apps. Trigger phrases: developer onboarding, time to first value, quickstart guide, hello world tutorial, developer activation, onboarding checklist, sample apps, getting started experience, reduce...'
-risk: unknown
+risk: critical
 source: https://github.com/jonathimer/devmarketing-skills/tree/main/skills/developer-onboarding
 source_repo: jonathimer/devmarketing-skills
 source_type: community

package/bundled-skills/developer-sandbox/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: developer-sandbox
 description: 'Design and build interactive playgrounds that let developers experience your product without commitment. This skill covers playground architecture, pre-populated examples, embedding strategies, gating decisions, and converting playground users to signups. Trigger phrases: "developer...'
-risk: unknown
+risk: critical
 source: https://github.com/jonathimer/devmarketing-skills/tree/main/skills/developer-sandbox
 source_repo: jonathimer/devmarketing-skills
 source_type: community

package/bundled-skills/developer-seo/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: developer-seo
 description: 'SEO strategy for technical queries and developer audiences. Covers keyword research for "how to X in language" queries, error message SEO, Stack Overflow-style content, technical long-tail keywords, and competing with official documentation sites. Use when asked about: - SEO for...'
-risk: unknown
+risk: critical
 source: https://github.com/jonathimer/devmarketing-skills/tree/main/skills/developer-seo
 source_repo: jonathimer/devmarketing-skills
 source_type: community

package/bundled-skills/developer-signup-flow/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: developer-signup-flow
 description: "Design frictionless signup experiences for developers including GitHub OAuth, API key generation, and onboarding personalization. Trigger phrases: developer signup, dev registration, OAuth flow, API key onboarding, reduce signup friction, developer authentication, signup conversion,..."
-risk: unknown
+risk: critical
 source: https://github.com/jonathimer/devmarketing-skills/tree/main/skills/developer-signup-flow
 source_repo: jonathimer/devmarketing-skills
 source_type: community

package/bundled-skills/devops-troubleshooter/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: devops-troubleshooter
 description: Expert DevOps troubleshooter specializing in rapid incident response, advanced debugging, and modern observability.
-risk: unknown
+risk: critical
 source: community
 date_added: '2026-02-27'
 ---

package/bundled-skills/devrel-content/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: devrel-content
 description: When the user wants to create technical content for developers including blog posts, tutorials, and documentation. Trigger phrases include "write a blog post," "technical article," "developer content," "tutorial," "devrel content," "dev blog," "technical writing," or "content for...
-risk: unknown
+risk: critical
 source: https://github.com/jonathimer/devmarketing-skills/tree/main/skills/devrel-content
 source_repo: jonathimer/devmarketing-skills
 source_type: community

package/bundled-skills/differential-review/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: differential-review
 description: "Security-focused code review for PRs, commits, and diffs."
-risk: unknown
+risk: critical
 source: community
 ---
 

package/bundled-skills/discord-bot-architect/SKILL.md

@@ -3,7 +3,7 @@ name: discord-bot-architect
 description: Specialized skill for building production-ready Discord bots.
   Covers Discord.js (JavaScript) and Pycord (Python), gateway intents, slash
   commands, interactive components, rate limiting, and sharding.
-risk: unknown
+risk: critical
 source: vibeship-spawner-skills (Apache 2.0)
 date_added: 2026-02-27
 ---

package/bundled-skills/dispatching-parallel-agents/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: dispatching-parallel-agents
 description: "Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies"
-risk: unknown
+risk: critical
 source: community
 date_added: "2026-02-27"
 ---

package/bundled-skills/distributed-debugging-debug-trace/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: distributed-debugging-debug-trace
 description: "You are a debugging expert specializing in setting up comprehensive debugging environments, distributed tracing, and diagnostic tools. Configure debugging workflows, implement tracing solutions, and establish troubleshooting practices for development and production environments."
-risk: unknown
+risk: critical
 source: community
 date_added: "2026-02-27"
 ---

package/bundled-skills/django-access-review/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: django-access-review
 description: django-access-review
-risk: unknown
+risk: critical
 source: community
 ---
 

package/bundled-skills/django-perf-review/SKILL.md

@@ -3,7 +3,7 @@ name: django-perf-review
 description: Django performance code review. Use when asked to "review Django performance", "find N+1 queries", "optimize Django", "check queryset performance", "database performance", "Django ORM issues", or audit Django code for performance problems.
 allowed-tools: Read, Grep, Glob, Bash, Task
 license: LICENSE
-risk: unknown
+risk: critical
 source: community
 ---
 

package/bundled-skills/django-pro/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: django-pro
 description: Master Django 5.x with async views, DRF, Celery, and Django Channels. Build scalable web applications with proper architecture, testing, and deployment.
-risk: unknown
+risk: critical
 source: community
 date_added: '2026-02-27'
 ---

package/bundled-skills/doc-coauthoring/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: doc-coauthoring
 description: "This skill provides a structured workflow for guiding users through collaborative document creation. Act as an active guide, walking users through three stages: Context Gathering, Refinement & Structure, and Reader Testing."
-risk: unknown
+risk: critical
 source: community
 date_added: "2026-02-27"
 ---

package/bundled-skills/docker-expert/SKILL.md

@@ -2,7 +2,7 @@
 name: docker-expert
 description: "You are an advanced Docker containerization expert with comprehensive, practical knowledge of container optimization, security hardening, multi-stage builds, orchestration patterns, and production deployment strategies based on current industry best practices."
 category: devops
-risk: unknown
+risk: critical
 source: community
 date_added: "2026-02-27"
 ---

package/bundled-skills/docs/contributors/security-guardrails.md

@@ -21,8 +21,13 @@ Every offensive skill **MUST** begin with this exact disclaimer in its `SKILL.md
 
 Offensive skills must **NEVER** run fully autonomously.
 
-- **Requirement**: The skill description/instructions must explicitly tell the agent to _ask for user confirmation_ before executing any exploit or attack command.
-- **Agent Instruction**: "Ask the user to verify the target URL/IP before running."
+- **Requirement**: Before each command that probes, exploits, changes, persists
+  on, extracts data from, or attempts credential access against a target, the
+  agent must collect the exact target, written-authorization confirmation, and
+  permitted scope; show the exact command and expected effect; and wait for
+  explicit confirmation in the current conversation.
+- Without that confirmation, the skill must remain read-only and provide
+  defensive guidance only.
 
 ### 3. Safe by Design
 
@@ -42,6 +47,18 @@ _Examples: Linting, Log Analysis, Configuration Auditing._
 - **Documentation review**: Defensive skills with command examples must still be reviewed for unsafe command patterns.
 - **High-risk examples** (`curl|bash`, `wget|sh`, etc.) must use explicit allowlisting comments and clear warning context in the skill body when retained for operational examples.
 
+## External Source Installation
+
+- Do not clone or download a moving branch directly into an active skills,
+  plugin, hook, or agent-configuration directory.
+- Pin external examples to a full reviewed commit or immutable release, clone to
+  a temporary review directory, and inspect every bundled file before activation.
+- Report scripts, package lifecycle hooks, symlinks, binaries, network access,
+  credential handling, privileged actions, and destructive operations.
+- Obtain explicit user approval before downloading and again before copying,
+  installing dependencies, enabling hooks, or changing agent configuration.
+- A pin provides reproducibility, not proof of trust; upgrading requires a new review.
+
 ---
 
 ## ⚖️ Legal Disclaimer

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 1,991+ skills."
+description: "Use agentic-awesome-skills with Jetski/Cortex without hitting context-window overflow with 1,994+ skills."
 ---
 
-# Jetski/Cortex + Gemini: safe integration with 1,991+ skills
+# Jetski/Cortex + Gemini: safe integration with 1,994+ 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 1,991+ skills, this approach fills the context window before user messages are even added, causing truncation.
+With 1,994+ 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 1,991+ skills installed.
+This pattern avoids context overflow when you have 1,994+ skills installed.
 
 Manifest contract references:
 

package/bundled-skills/docs/maintainers/merge-batch.md

@@ -42,6 +42,7 @@ Use `--dry-run` to exercise local classification without approving a run or merg
 - fetch the exact base/head objects and classify the complete raw Git diff
 - recompute changed-skill evidence with evaluator code materialized from the trusted `main` commit
 - reject incomplete evidence coverage, deterministic quality/security/provenance regressions, and base/head drift
+- allow only exact `source_repo` transitions recorded in the trusted protected-base provenance exception ledger; unrecorded or malformed transitions still fail closed
 - for external PRs, poll for asynchronously-created fork runs and approve only runs waiting on `action_required` when every path, mode, object, size, and workflow identity is allowlisted
 - for sensitive same-repository source changes, allow the guarded exception only when the PR author is the repository owner and the exact full head SHA is attested; collaborator-authored sensitive changes fail closed under the external safety policy
 - wait for the latest required checks bound to the exact head SHA

package/bundled-skills/docs/maintainers/pr-autonomy.md

@@ -62,7 +62,7 @@ A successful `manual-review-required` check means only that the requirement was
 4. for external PRs, rejects unsafe paths, modes, symlinks, gitlinks, executable files, unknown types, oversized blobs, incomplete metadata, or non-allowlisted workflows;
 5. verifies workflow event, workflow identity, pull-request number, and head SHA;
 6. recomputes changed-skill evidence over the exact merge-base-to-head record set and requires one-to-one coverage of every skill-content Git record;
-7. rejects operational errors, malformed evidence, incomplete snapshots, score-component regressions, provenance identity regressions, or any other deterministic blocker;
+7. rejects operational errors, malformed evidence, incomplete snapshots, score-component regressions, provenance identity regressions, or any other deterministic blocker; an exact `source_repo` rename may pass only when the trusted protected-base ledger records the skill, old slug, new slug, upstream repository ID, verification date, and canonical GitHub URL;
 8. re-reads both pull-request base and head before and after approval and immediately before merge.
 
 A real merge also requires effective server-side protection for `main`: the four exact GitHub-Actions-owned checks (`pr-policy`, `pr-evidence`, `source-validation`, and `artifact-preview`), strict up-to-date enforcement, pull-request-only changes, administrator enforcement, no applicable ruleset bypass actors, and no merge queue. If that enforcement cannot be proven, `merge:batch` refuses non-dry-run operation. `merge:batch` does not retry base drift automatically or reuse stale evidence; the batch must be rerun from the new tuple. Pre-existing auto-merge state is rejected, and the immediate GitHub merge endpoint must return `merged: true` before post-merge work begins.
@@ -96,7 +96,7 @@ Each phase requires evidence from the previous phase before activation:
 3. Keep `main` protected by stable app-bound checks and remove any newly introduced direct writer.
 4. Add schema-validated fork-safe semantic review whose privileged code always comes from the protected base.
 5. Build deterministic release-candidate pull requests with rendering separated from publication.
-6. Add immutable upstream commit/path/hash provenance and a delta-based exception ledger.
+6. Expand immutable upstream commit/path/hash provenance. The first narrow delta exception ledger now covers maintainer-verified `source_repo` renames only; broader provenance exceptions remain out of scope.
 7. Consider auto-merge only for empirically proven documentation or metadata classes. New skills, security-sensitive content, workflows, installers, releases, provenance exceptions, and policy changes remain human decisions.
 
 Merge queue is not part of the current plan. The repository is personally owned, and its workflows do not currently support a `merge_group` event.

package/bundled-skills/docs/maintainers/provenance-identity-exceptions.json

@@ -0,0 +1,14 @@
+{
+  "schema_version": 1,
+  "exceptions": [
+    {
+      "skill_id": "modellix",
+      "field": "source_repo",
+      "before": "Modellix/modellix-skill",
+      "after": "Modellix/modellix-plugin",
+      "upstream_repository_id": 1150322983,
+      "verified_at": "2026-07-28",
+      "evidence_url": "https://github.com/Modellix/modellix-plugin"
+    }
+  ]
+}

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 `1,991+ Agentic Skills` as supporting catalog evidence, not a second product;
+- present `1,994+ 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 1,991+ skills from the skills directory
+- All 1,994+ 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.5.1 -- aas mcp configure \
+npm exec --yes --ignore-scripts --package=agentic-awesome-skills@15.7.0 -- aas mcp configure \
   --host codex \
   --scope user \
   --config /absolute/path/to/codex/config.toml \

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

@@ -1062,4 +1062,4 @@ Found a skill that should be in a bundle? Or want to create a new bundle? [Open
 
 ---
 
-_Last updated: June 2026 | Total Skills: 1,991+ | Total Bundles: 58_
+_Last updated: June 2026 | Total Skills: 1,994+ | 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 1,991+ skills instead of a narrow single-domain starter pack.
+- It includes 1,994+ 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/faq.md

@@ -31,6 +31,11 @@ Skills are specialized instruction files that teach AI assistants how to handle
 
 **No.** With AAS Core, ask the agent to inspect the project and choose the exact skills from the complete catalog. On a broad direct install, all skills may be present locally while the host loads only the skills it invokes.
 
+The direct installer keeps its historical full-catalog default for compatibility,
+but now shows the risk distribution before writing. Use `audit --skills <ids>` to
+read an exact selection and its bundled files without executing them, then use
+the same `--skills` selection with `--dry-run` before installation.
+
 Use [Starter Packs](bundles.md) as human-curated presets when you want a fixed starting point.
 
 If you want a narrower install surface for **Claude Code** or **Codex**, use the new plugin distributions documented in [plugins.md](plugins.md) instead of the full library install.
@@ -128,8 +133,13 @@ We classify skills so you know what you're running. These values map directly to
 
 ### Can these skills hack my computer?
 
-**No.** Skills are text files. However, they _instruct_ the AI to run commands. If a skill says "delete all files", a compliant AI might try to do it.
-_Always check the Risk label and review the code._
+A Markdown file is not a running process, but calling it “just text” is not a
+sufficient security model. A loaded skill can instruct an agent to run commands,
+use credentials, access the network, or modify files. Installation alone is not
+evidence that any of that happened; execution logs and resulting system changes
+are. Review the exact skill and every bundled file before use, keep agent
+permissions narrow, and require confirmation for consequential actions. See
+[Security, trust, and antivirus alerts](security-and-antivirus.md).
 
 ---
 

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 1,991+ files.
+- It helps new users get started with bundles and workflows rather than forcing a cold start from 1,994+ 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/getting-started.md

@@ -48,6 +48,20 @@ npx agentic-awesome-skills
 This clones to `~/.agents/skills` by default. Use `--cursor`, `--claude`, `--gemini`, `--codex`, `--kiro`, or `--agy` to install for a specific tool, or `--path <dir>` for a custom location. Run `npx agentic-awesome-skills --help` for details.
 The installer uses a shallow clone by default so you get the current library without paying for the full git history on first install.
 
+With no selector, the legacy-compatible default installs the complete catalog
+and prints a risk summary before writing. That includes `unknown`, `critical`,
+and authorized-use-only `offensive` skills. Installed text is not automatically
+executed, but it can influence an agent when loaded, so review an exact set first:
+
+```bash
+npx agentic-awesome-skills audit --skills brainstorming,backend-dev-guidelines
+npx agentic-awesome-skills --skills brainstorming,backend-dev-guidelines --dry-run
+```
+
+You can also ask your agent to read the selected `SKILL.md` and every bundled
+file before installation. The static audit reports risky capabilities; it does
+not prove that a skill is safe. See [Security, trust, and antivirus alerts](security-and-antivirus.md).
+
 If you see a 404 error, use: `npx github:sickn33/agentic-awesome-skills`
 
 **Option B — git clone:**

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 1,991+ specialized areas
+- **Domain expertise** across 1,994+ 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/security-and-antivirus.md

@@ -0,0 +1,63 @@
+# Security, Trust, and Antivirus Alerts
+
+## The trust boundary
+
+A skill is instruction content, not an executable process. Copying a `SKILL.md`
+does not itself run the commands it contains. The security boundary changes when
+an agent loads those instructions and receives permission to use a shell,
+network, credentials, filesystem, browser, MCP server, or other tool.
+
+Treat every community skill and every bundled file as untrusted input until you
+have reviewed the exact installed revision. A risk label describes intended
+capability; it is not a malware verdict or safety certificate. Repository stars,
+contributors, Markdown-only packaging, and a commit pin are not substitutes for
+review.
+
+## Review before installation
+
+Use an exact selection and inspect it without execution:
+
+```bash
+npx agentic-awesome-skills audit --skills <skill-id,skill-id>
+npx agentic-awesome-skills --skills <skill-id,skill-id> --dry-run
+```
+
+The audit recursively reads the selected skill directories and reports command,
+network, credential, filesystem, privileged, destructive, symlink, and binary
+signals. Read the files behind every finding and ask your agent to explain them.
+Static pattern matching can miss dangerous logic and can flag legitimate
+security examples, so a clean report does not prove safety.
+
+For external sources, require a full commit pin or immutable release, download
+to a temporary review directory, inspect package scripts and every bundled file,
+and approve the final copy separately. Do not pipe remote content into a shell or
+clone a moving branch directly into an active agent directory.
+
+## If antivirus flags a skill
+
+Security documentation often contains exploit names, commands, or payload
+fragments that signature scanners recognize. A detection in Markdown can be a
+correct content detection without showing that a Trojan executed. Do not dismiss
+it, but distinguish content from activity:
+
+1. Stop the agent and quarantine or move the flagged skill out of active paths.
+2. Record the exact file, detector name, package version, and file hash.
+3. Review the file and adjacent bundled content without executing anything.
+4. Check agent transcripts, shell history, process logs, downloads, persistence
+   locations, credential access, and unexpected filesystem or network changes.
+5. Run your operating system's trusted security scan. Rotate credentials only
+   when exposure or suspicious activity is plausible; reinstall the system when
+   forensic evidence or incident-response guidance justifies it, not solely
+   because a text signature matched.
+6. Report reproducible findings privately through the process in
+   [`SECURITY.md`](../../SECURITY.md). Include evidence of execution or impact
+   separately from the flagged text.
+
+## Safer operating defaults
+
+- Install only the skills needed for the task when practical.
+- Keep agent permissions least-privileged and avoid administrator access.
+- Require current-conversation approval for destructive, privileged, financial,
+  account-write, credential, publishing, and offensive-security actions.
+- Use disposable environments for offensive or untrusted workflows.
+- Preserve logs and backups so actions can be audited and reversed where possible.

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 1,991+ skill files** to your computer (default: `~/.agents/skills/`; or a custom path like `~/.agent/skills/` if you used `--path`)
+✅ **Downloaded 1,994+ 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 1,991+ skills at once. Here's a sensible approach:
+Don't try to use all 1,994+ 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 1,991+ skills installed locally, you should **not** concatenate every `SKILL.md` into a single system prompt or context block.
+No. Even though you have 1,994+ 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/                          ← 1,991+ skills live here
+├── 📁 skills/                          ← 1,994+ skills live here
 │   │
 │   ├── 📁 brainstorming/
 │   │   └── 📄 SKILL.md                 ← Skill definition
@@ -53,7 +53,7 @@ agentic-awesome-skills/
 │   │   └── 📁 2d-games/
 │   │       └── 📄 SKILL.md             ← Nested skills also supported
 │   │
-│   └── ... (1,991+ total)
+│   └── ... (1,994+ total)
 │
 ├── 📁 apps/
 │   └── 📁 web-app/                     ← Interactive browser
@@ -106,7 +106,7 @@ agentic-awesome-skills/
 
 ```
                     ┌─────────────────────────┐
-                    │  1,991+ SKILLS          │
+                    │  1,994+ SKILLS          │
                     └────────────┬────────────┘
                                  │
         ┌────────────────────────┼────────────────────────┐
@@ -207,7 +207,7 @@ If you want a workspace-style manual install instead, cloning into `.agent/skill
 │   ├── 📁 brainstorming/                 │
 │   ├── 📁 stripe-integration/            │
 │   ├── 📁 react-best-practices/          │
-│   └── ... (1,991+ total)                │
+│   └── ... (1,994+ total)                │
 └─────────────────────────────────────────┘
 ```