- 📄 SKILL.md
skill-foo
A sample skill for integration testing of windsurf/cursor migration
A sample skill for integration testing of windsurf/cursor migration
Atlas database migration tool best practices and usage. Use when creating migrations, modifying database schemas, troubleshooting migration errors, or answering questions about Atlas workflow (diff, apply, lint, hash, versioned migrations). --- # Atlas Migrations Atlas is a declarative database schema management tool. You declare the desired schema state, Atlas generates the migration SQL to get there. ## Core Concept Atlas uses a **declarative** approach: 1. You edit schema source files (the desired state). 2. Atlas compares desired state vs. current migration history. 3. Atlas generates the migration SQL automatically. You never write migration SQL by hand. ## Project Layout ``` atlas.hcl # Atlas configuration internal/db/ schemas/ main.sql # Entry point — imports all tables tables/ auth_user.sql # One file per table auth_session.sql shop_order.sql migrations/ 20260317041843_description.sql # Generated migrations (never edit) atlas.sum # Integrity hash (never edit) queries/ # sqlc query files (separate concern) ``` ## Configuration (atlas.hcl) ```hcl variable "dev_url" { type = string default = "sqlite://dev?mode=memory" } env "local" { src = "file://internal/db/schemas/main.sql" dev = var.dev_url migration { dir = "file://internal/db/migrations" } } ```
Add new field to .agents.yml config schema (updates init.md templates, version, migration)
Invoke for technology replacement, migration, modernization, or conversion in Android/Kotlin projects — even when user asks where to start or whether feasible. Triggers: \"moving off [library]\", \"switch to Y\", \"replace X with Y\", \"migrate from X to Y\", \"modernize\", \"convert to Compose\", \"upgrade from [old version]\", \"drop/ditch [library]\". Covers: async rewrites (RxJava→coroutines, AsyncTask→coroutines, EventBus→Flow), UI rewrites (XML→Compose or reverse), library swaps (Glide→Coil, Retrofit→Ktor), Java→Kotlin conversion, Gradle upgrades (Groovy→Kotlin DSL). Also: user asks which tech to use for modernization (e.g., \"AsyncTask — coroutines or executors?\"). Do NOT use for: KMP structural migration (use kmp-migration), debugging without migration intent, new features, Kotlin version bumps, or non-Android/Kotlin migrations.
Use when changing libs/database/src/schema.ts, adding Drizzle migrations, debugging drizzle-kit drift, or deciding between auto-generated and custom SQL migrations. Includes the post-#867 baseline-reset rule.
Create a new deploy/migrations/NNNN_*.sh migration file for any incompatible CCC change (new/removed/modified service files, cron changes, config updates). Invoke whenever you add, remove, or meaningfully change a file in deploy/systemd/, deploy/launchd/, or deploy/crontab-acc.txt — or whenever a change requires action on already-deployed nodes to stay current. --- You are adding a CCC deploy migration. A migration is a numbered shell script in `deploy/migrations/` that runs exactly once per agent node, tracked in `~/.ccc/migrations.json`. ## Step 1 — Gather context
explain, graph, migrate, init, analyze, apply. Usar siempre que el usuario
skill-sample/ ├─ SKILL.md ⭐ Required: skill entry doc (purpose / usage / examples / deps) ├─ manifest.sample.json ⭐ Recommended: machine-readable metadata (index / validation / autofill) ├─ LICENSE.sample ⭐ Recommended: license & scope (open source / restriction / commercial) ├─ scripts/ │ └─ example-run.py ✅ Runnable example script for quick verification ├─ assets/ │ ├─ example-formatting-guide.md 🧩 Output conventions: layout / structure / style │ └─ example-template.tex 🧩 Templates: quickly generate standardized output └─ references/ 🧩 Knowledge base: methods / guides / best practices ├─ example-ref-structure.md 🧩 Structure reference ├─ example-ref-analysis.md 🧩 Analysis reference └─ example-ref-visuals.md 🧩 Visual reference
More Agent Skills specs Anthropic docs: https://agentskills.io/home
├─ ⭐ Required: YAML Frontmatter (must be at top) │ ├─ ⭐ name : unique skill name, follow naming convention │ └─ ⭐ description : include trigger keywords for matching │ ├─ ✅ Optional: Frontmatter extension fields │ ├─ ✅ license : license identifier │ ├─ ✅ compatibility : runtime constraints when needed │ ├─ ✅ metadata : key-value fields (author/version/source_url...) │ └─ 🧩 allowed-tools : tool whitelist (experimental) │ └─ ✅ Recommended: Markdown body (progressive disclosure) ├─ ✅ Overview / Purpose ├─ ✅ When to use ├─ ✅ Step-by-step ├─ ✅ Inputs / Outputs ├─ ✅ Examples ├─ 🧩 Files & References ├─ 🧩 Edge cases ├─ 🧩 Troubleshooting └─ 🧩 Safety notes
Skill files are scattered across GitHub and communities, difficult to search, and hard to evaluate. SkillWink organizes open-source skills into a searchable, filterable library you can directly download and use.
We provide keyword search, version updates, multi-metric ranking (downloads / likes / comments / updates), and open SKILL.md standards. You can also discuss usage and improvements on skill detail pages.
Quick Start:
Import/download skills (.zip/.skill), then place locally:
~/.claude/skills/ (Claude Code)
~/.codex/skills/ (Codex CLI)
One SKILL.md can be reused across tools.
Everything you need to know: what skills are, how they work, how to find/import them, and how to contribute.
A skill is a reusable capability package, usually including SKILL.md (purpose/IO/how-to) and optional scripts/templates/examples.
Think of it as a plugin playbook + resource bundle for AI assistants/toolchains.
Skills use progressive disclosure: load brief metadata first, load full docs only when needed, then execute by guidance.
This keeps agents lightweight while preserving enough context for complex tasks.
Use these three together:
Note: file size for all methods should be within 10MB.
Typical paths (may vary by local setup):
One SKILL.md can usually be reused across tools.
Yes. Most skills are standardized docs + assets, so they can be reused where format is supported.
Example: retrieval + writing + automation scripts as one workflow.
Some skills come from public GitHub repositories and some are uploaded by SkillWink creators. Always review code before installing and own your security decisions.
Most common reasons:
We try to avoid that. Use ranking + comments to surface better skills: