avav25/ai-assets
.windsurf/skills/ai-assets/SKILL.md
Create, modify, validate, and analyze Windsurf AI assets such as AGENTS.md files, Windsurf skills, templates, and supporting scripts. Use when building or maintaining the repository's Windsurf-specific AI component package.
development
Updated Apr 16, 2026
$ install --global
skillsauthnpx skillsauth add avav25/ai-assets ai-assetsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 16, 2026, 1:05 AM42.3s28 files scanned
SKILL.md
- name:
- ai-assets
- description:
- Create, modify, validate, and analyze Windsurf AI assets such as AGENTS.md files, Windsurf skills, templates, and supporting scripts. Use when building or maintaining the repository's Windsurf-specific AI component package.
AI Assets
Build and maintain Windsurf-native AI assets for this repository. Treat every asset as live Windsurf prompt surface.
1. Determine Scope
Identify:
- Operation:
create|modify|validate|analyze - Asset type:
agents-md|skill|template|checklist|script - Target path or asset name
If the request is ambiguous, resolve it from repository context before asking the user.
2. Gather Context
Read only the assets needed for the task:
- The target asset, if it exists
- Root
AGENTS.md - Relevant scoped
AGENTS.mdfiles - Relevant
.windsurf/skills/*/SKILL.mdfiles - Relevant files under
.windsurf/ context-engineeringskill when the asset affects prompt layering, memory, RAG, or orchestration
3. Build a Dependency Map
Map outgoing and incoming references.
Check for:
- References to
AGENTS.md - References to
.windsurf/skills/<name>/ - References to shared templates, checklists, or support resources under
.windsurf/skills/ai-assets/ - References to explicit support scripts such as
.windsurf/hooks/scripts/* - Missing files
- Orphaned assets
- Circular references that add confusion
For analyze, stop after presenting the dependency map.
4. Choose the Right Windsurf Primitive
Use the smallest asset that matches the job:
- Repository or directory policy ->
AGENTS.md - Reusable task workflow or knowledge ->
.windsurf/skills/<name>/SKILL.md - Reusable authoring scaffold -> supporting resources under
.windsurf/skills/<skill>/templates/ - Validation procedure -> supporting resources under
.windsurf/skills/<skill>/checklists/or companion markdown files - Repeatable local automation -> explicit support scripts owned by the target package
Do not recreate Claude-specific primitives such as agent files, Claude settings, or Claude hook configs.
5. Authoring Rules
AGENTS.md
- Put hard constraints first
- Keep project facts concrete and current
- Keep global policy in the root file and local conventions in scoped files
- Avoid repeating parent guidance verbatim
SKILL.md
- Include
nameand a specificdescription - Optimize
descriptionfor correct progressive disclosure - Keep the workflow executable with minimal ambiguity
- Move bulky references and checklists into companion markdown files
Templates and Checklists
- Prefer short, reusable structures
- Separate policy from examples
- Make completion criteria explicit
Scripts
- Keep scripts visible and optional
- Never hide critical behavior behind implicit automation
- Prefer PowerShell for this repository's local automation
6. Prompt Engineering Review
Review the asset as live Windsurf context:
- What part of Windsurf behavior does it shape?
- What failure mode does it prevent or enable?
- Is the instruction hierarchy clear?
- Is critical information front-loaded?
- Is the token cost justified?
Use review-checklist.md for the full validation pass.
7. Validate
Run these checks on every create or modify operation:
- Asset uses Windsurf-native concepts only
- References resolve
- No machine-specific paths unless intentionally local documentation
- No secrets or credentials
- English only
SKILL.mdremains concise enough for progressive disclosureAGENTS.mdguidance is specific, not generic
If the asset changes the Windsurf package structure, update the package README or mapping docs.
8. Finalize
Report:
- What changed
- Dependency status
- Validation result
- Remaining follow-up items
Related Skills
avav25/knowledge-sync
development
VerifiedTrustedCommunity
Use this skill when running the recurring (daily) knowledge-base rescan for a repo that already has knowledge/.knowledge-sync.yml — the main-thread dispatcher that reads the config, computes the git delta since last_scanned_sha, maps changed paths to affected doc areas, early-exits cheaply when nothing changed, then fans out one Agent(content-writer) per affected area, applies the propose/direct update policy, advances the baseline only on success, and writes an L4 run log — all with the G1 untrusted-content choke-point, secret-scan, deny-list, and budget controls woven in. For first-time setup use /knowledge-sync-init.
1SKILL.mdUpdated May 24, 2026
avav25/knowledge-sync-init
development
VerifiedTrustedCommunity
Use this skill when bootstrapping scheduled knowledge-base sync for a repo that has no knowledge/.knowledge-sync.yml yet — to run one-time setup that detects the knowledge_root from CLAUDE.md/AGENTS.md, maps doc areas to source globs, records opt-in external sources (Linear/Notion/WebFetch, all disabled by default), captures a baseline last_scanned_sha, sets the per-area update policy, generates or seeds knowledge/CONVENTIONS.md, provisions the L4 memory dir, and offers to register the daily routine. Routes ongoing recurring sync operations to /knowledge-sync.
1SKILL.mdUpdated May 24, 2026
avav25/ai-skills-init
tools
VerifiedTrustedCommunity
Use this skill when bootstrapping a target repository to be ai-skills-aware — on the first run of any ai-skills workflow in a fresh repo, when adopting the ai-skills plugin in an existing repo, or after upgrading to a plugin version that adds new memory paths or templates, including when the user does not say "init" but asks to "set up" or "onboard" the repo — to detect codebase type, create CLAUDE.md + AGENTS.md scaffolding, initialize the .ai-skills-memory/ directory tree from L1 templates, and configure .gitignore. Idempotent — safe to re-run. Accepts `--codebase-type <type>` and `--overwrite`. Not for re-initializing only memory — use `/memory-init` instead.
1SKILL.mdUpdated May 18, 2026
avav25/plugin-author
tools
VerifiedTrustedCommunity
Use this skill when extending, repairing, or improving plugin assets, when ingesting a `/feedback` report as a fix-cycle backlog, or when you do not remember which lower-level command is right for the job — the umbrella workflow for ai-skills plugin-asset authoring and maintenance: creating, auditing, fixing, improving, refactoring, and migrating skills, agents, rules, hooks, prompts, schemas, and rubrics inside the plugin. Auto-classifies the request, loads the right knowledge skills (`@prompt-engineering`, `@context-engineering`, `@team-protocols`), and spawns the right subagents (`prompt-engineer`, `system-architect`, `python-engineer`, `software-engineer`, `qa-engineer`, `eval-judge`) via the `Agent` tool.
1SKILL.mdUpdated May 14, 2026