rzyfront/skill-creator
skills/skill-creator/SKILL.md
Creates or updates Vendix AI agent skills using the repository skill standard. Trigger: When creating a new skill, updating skill guidance, documenting repeatable AI patterns, or resolving a knowledge gap.
$ install --global
skillsauthnpx skillsauth add rzyfront/vendix skill-creatorInstall 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: May 16, 2026, 5:00 AM98.1s2 files scanned
SKILL.md
- name:
- skill-creator
- description:
- >
- Trigger:
- When creating a new skill, updating skill guidance, documenting repeatable AI patterns, or resolving a knowledge gap.
- license:
- MIT
- author:
- rzyfront
- version:
- 1.0
- scope:
- [root]
- allowed-tools:
- Read, Edit, Write, Glob, Grep, Bash, WebFetch, WebSearch, Task
Skill Creator
Purpose
Use this skill to create or update reusable AI guidance for Vendix. Skills should be compact, accurate, scoped to one responsibility, and synchronized through skill-sync.
When To Create Or Update A Skill
Create or update a skill when:
- A pattern is repeated across tasks and agents need consistent guidance.
- Vendix behavior differs from generic framework defaults.
- A workflow needs explicit decision rules, commands, or safety constraints.
- A plan step exposes a knowledge gap that should become reusable guidance.
Do not create a skill for one-off instructions, obvious conventions, or content already covered by an accurate existing skill.
Skill Standard
Each skill should have:
- One clear owner scope and purpose.
- Frontmatter with
name,description,license,metadata.author,metadata.version, and usuallymetadata.scopeplusmetadata.auto_invoke. - Critical rules first.
- Minimal examples only when they prevent mistakes.
- References to related skills instead of duplicating their rules.
- No stale project names, provider-specific assumptions, or absolute user paths.
Frontmatter Template
---
name: vendix-example-skill
description: >
Short description of what this skill governs.
Trigger: Specific action, file type, domain, or workflow that should load it.
license: MIT
metadata:
author: rzyfront
version: "1.0"
scope: [root]
auto_invoke:
- "Specific action that should load this skill"
allowed-tools: Read, Edit, Write, Glob, Grep, Bash
---
allowed-tools is optional and belongs at the top level. Keep metadata.auto_invoke specific enough to avoid loading unrelated skills.
Content Template
# Skill Title
## Purpose
[What this skill governs and what it does not govern]
## Core Rules
- [Most important rules]
## Workflow
1. [Only if this skill requires sequence]
## Decision Rules
| Situation | Use |
| --- | --- |
| [Condition] | [Action] |
## Related Skills
- `other-skill` - [why it is related]
Update Workflow
- Check whether an existing skill should be updated instead of creating a new one.
- Read related skills to avoid duplication.
- Edit only the source skill under
skills/. - Keep guidance compact and current with the real codebase.
- Run
./skills/skill-sync/assets/sync.sh. - Run
./skills/setup.sh --sync. - Verify generated provider copies and
AGENTS.mdauto-invoke entries.
Naming Rules
| Skill Type | Pattern | Examples |
| --- | --- | --- |
| Workflow | {action}-{target} | skill-creator, buildcheck-dev |
| Vendix domain | vendix-{domain} | vendix-subscription-gate |
| Vendix app/layer | vendix-{layer}-{topic} | vendix-frontend-routing |
| AI platform | vendix-ai-{topic} | vendix-ai-streaming |
Related Skills
skill-sync- Required after creating or modifying skillshow-to-plan- Marks knowledge gaps that may become skillshow-to-dev- Requires loading relevant skills before development
Related Skills
rzyfront/mobile-dev
development
VerifiedTrustedCommunity
Mobile app development rules for Vendix Expo/React Native project. Trigger: When editing, creating, or modifying any file under apps/mobile, or when developing mobile-specific features.
5SKILL.mdUpdated May 29, 2026
rzyfront/vendix-subscription-gate
development
VerifiedTrustedCommunity
Feature gating by store subscription state: global store write guard, AI feature gate, Redis feature resolution, quota consumption, frontend paywall interceptor, banner, and subscription UI states. Trigger: When adding feature gates, paywalls, subscription-based access control, protecting store write operations, AI feature gates, or rollout flags.
5SKILL.mdUpdated May 16, 2026
rzyfront/vendix-saas-billing
testing
VerifiedTrustedCommunity
SaaS subscription billing for Vendix stores: plan pricing, invoices, Wompi platform payments, manual payments, partner commissions, payouts, proration, and dunning. Trigger: When creating SaaS invoices, working with partner rev-share, margin/surcharge pricing, invoice sequence allocation, partner payout batches, subscription payments, manual payments, or dunning flows.
5SKILL.mdUpdated May 16, 2026
rzyfront/vendix-redis-quota
development
VerifiedTrustedCommunity
Periodic quota counters with Redis, UTC period keys, Lua-based idempotent AI quota consumption, request-id deduplication, and post-success consumption. Trigger: When building quota counters, enforcing monthly/daily feature caps, or reusing AI quota patterns for uploads, emails, exports, or rate-limited features.
5SKILL.mdUpdated May 16, 2026