Markbind Typescript Migration
MarkBind/markbind
Complete guide for migrating JavaScript files to TypeScript in the MarkBind project, including the two-commit strategy, import/export syntax conversion, and best practices.
A skill your agent uses when writing, reviewing, or debugging Vue.js forms that import vee-validate (useForm, defineField, useField, useFieldArray, Form, Field, FieldArray, ErrorMessage).
Install Vee Validate Skilld
$ npx skills add skilld-dev/vue-ecosystem-skills --skill vee-validate-skilld -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install skilld-dev/vue-ecosystem-skills vee-validate-skilld --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/skilld-dev/vue-ecosystem-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/vee-validate-skilld .claude/skills/vee-validate-skilld && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "vee-validate-skilld" agent skill from https://github.com/skilld-dev/vue-ecosystem-skills/tree/main/skills/vee-validate-skilld into .claude/skills/vee-validate-skilld/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vee-validate-skilld", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/skilld-dev/vue-ecosystem-skills/tree/main/skills/vee-validate-skilldType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add skilld-dev/vue-ecosystem-skills --skill vee-validate-skilld -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install skilld-dev/vue-ecosystem-skills vee-validate-skilld --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/skilld-dev/vue-ecosystem-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/vee-validate-skilld .agents/skills/vee-validate-skilld && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "vee-validate-skilld" agent skill from https://github.com/skilld-dev/vue-ecosystem-skills/tree/main/skills/vee-validate-skilld into .agents/skills/vee-validate-skilld/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vee-validate-skilld", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add skilld-dev/vue-ecosystem-skills --skill vee-validate-skilld -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install skilld-dev/vue-ecosystem-skills vee-validate-skilld --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/skilld-dev/vue-ecosystem-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/vee-validate-skilld .cursor/skills/vee-validate-skilld && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "vee-validate-skilld" agent skill from https://github.com/skilld-dev/vue-ecosystem-skills/tree/main/skills/vee-validate-skilld into .cursor/skills/vee-validate-skilld/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vee-validate-skilld", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/skilld-dev/vue-ecosystem-skills.git --path skills/vee-validate-skilld--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add skilld-dev/vue-ecosystem-skills --skill vee-validate-skilld -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install skilld-dev/vue-ecosystem-skills vee-validate-skilld --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/skilld-dev/vue-ecosystem-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/vee-validate-skilld .gemini/skills/vee-validate-skilld && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "vee-validate-skilld" agent skill from https://github.com/skilld-dev/vue-ecosystem-skills/tree/main/skills/vee-validate-skilld into .gemini/skills/vee-validate-skilld/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vee-validate-skilld", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install skilld-dev/vue-ecosystem-skills vee-validate-skilldInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add skilld-dev/vue-ecosystem-skills --skill vee-validate-skilld -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/skilld-dev/vue-ecosystem-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/vee-validate-skilld .github/skills/vee-validate-skilld && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "vee-validate-skilld" agent skill from https://github.com/skilld-dev/vue-ecosystem-skills/tree/main/skills/vee-validate-skilld into .github/skills/vee-validate-skilld/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vee-validate-skilld", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add skilld-dev/vue-ecosystem-skills --skill vee-validate-skilld -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install skilld-dev/vue-ecosystem-skills vee-validate-skilld --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/skilld-dev/vue-ecosystem-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/vee-validate-skilld .opencode/skills/vee-validate-skilld && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "vee-validate-skilld" agent skill from https://github.com/skilld-dev/vue-ecosystem-skills/tree/main/skills/vee-validate-skilld into .opencode/skills/vee-validate-skilld/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vee-validate-skilld", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
vee-validate-skilld- GitHub stars
- 181
- Token cost
- ~1.6k tokens
- SKILL.md length
- 443 words
- Files
- 7 (incl. references)
- Skills in repo
- 34
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when writing, reviewing, or debugging Vue.js forms that import vee-validate (useForm, defineField, useField, useFieldArray, Form, Field, FieldArray, ErrorMessage).
- Debugging Vue.js forms that import vee-validate (useForm
- SKILL.md covers Environment, Two API styles, Core rules and Validation modes, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Vee Validate Skilld is an agent skill from skilld-dev/vue-ecosystem-skills. Use when writing, reviewing, or debugging Vue.js forms that import vee-validate (useForm, defineField, useField, useFieldArray, Form, Field, FieldArray, ErrorMessage). Provides correct v4.15.x Composition API and component usage, validation schema patterns, typed-schema integration, version-specific API changes since 4.9, deprecations, and known pitfalls.
Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including reference files (for example `references/api-surface.md`, `references/components.md` and `references/composition-api.md`).
It sits in Development. It works with Vue.js and npm. The repository describes itself as: Agent Skills for the Vue ecosystem, written from current docs, issues, and releases. The licence is MIT.
When your agent uses it
- Debugging Vue.js forms that import vee-validate (useForm
Example prompts
- “/vee-validate-skilld”
What it can do on your machine
Read from SKILL.md and the folder at commit c8994af. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are vue).
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
vee-validate.logaretm.comgithub.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Vee Validate Skilld loads about 1.6k tokens when it runs, and up to ~7.5k if it reads all its reference files. Until then it costs about 94 tokens; SKILL.md has 443 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from skilld-dev/vue-ecosystem-skills at commit c8994af, republished under its MIT licence (© skilld-dev). 443 words, ~1,575 tokens.
Download SKILL.mdSave it as
.claude/skills/vee-validate-skilld/SKILL.md (or your agent's skills folder). This skill also uses 6 other files; get the full folder from GitHub.- name
- vee-validate-skilld
- description
- Use when writing, reviewing, or debugging Vue.js forms that import vee-validate (useForm, defineField, useField, useFieldArray, Form, Field, FieldArray, ErrorMessage). Provides correct v4.15.x Composition API and component usage, validation schema patterns, typed-schema integration, version-specific API changes since 4.9, deprecations, and known pitfalls.
vee-validate 4.15.1
Form validation for Vue 3. Facts below come from the prepared source (dist/vee-validate.d.ts, dist/vee-validate.mjs, package.json) and official docs at https://vee-validate.logaretm.com/v4/.
Environment
- Package
vee-validate@4.15.1(package.json:3). Requiresvue ^3.4.26as peer (package.json:42). - ESM + CJS,
sideEffects: false, single entryvee-validate(package.json:11-26). - v4 supports Vue 3 only. Vue 2 needs vee-validate 2.x/3.x (README:69-72).
- Schema adapters live in separate packages:
@vee-validate/yup,@vee-validate/zod,@vee-validate/valibot; global rules in@vee-validate/rules; messages in@vee-validate/i18n.
Two API styles
Composition API (preferred for new code). useForm + defineField + handleSubmit:
<script setup>
import { useForm } from 'vee-validate';
function required(value) {
return value ? true : 'This field is required';
}
const { defineField, handleSubmit, errors } = useForm({
validationSchema: { field: required },
});
const [field, fieldProps] = defineField('field');
const onSubmit = handleSubmit(values => {
console.log(values);
});
</script>
<template>
<form @submit="onSubmit">
<input v-model="field" v-bind="fieldProps" />
<span>{{ errors.field }}</span>
<button>Submit</button>
</form>
</template>Source: README:84-118, https://vee-validate.logaretm.com/v4/guide/composition-api/getting-started/
Declarative components. Form + Field with scoped slots:
<script setup>
import { Field, Form } from 'vee-validate';
function required(value) {
return value ? true : 'This field is required';
}
function onSubmit(values) {
console.log(values);
}
</script>
<template>
<Form v-slot="{ errors }" @submit="onSubmit">
<Field name="field" :rules="required" />
<span>{{ errors.field }}</span>
<button>Submit</button>
</Form>
</template>Source: README:122-153, https://vee-validate.logaretm.com/v4/guide/components/handling-forms/
Core rules
- Bind fields with
defineField(path, config?). It returns[model, props]; spread the props withv-bindand the model withv-model(dist/vee-validate.d.ts:443, https://vee-validate.logaretm.com/v4/api/use-form/#definefield). - Never write directly to
values.field; use thedefineFieldmodel,setFieldValue, oruseSetFieldValue. useFieldModel,defineComponentBinds, anddefineInputBindsare deprecated in favor ofdefineField(dist/vee-validate.d.ts:444-459).- Show errors only after interaction, e.g.
v-if="errorMessage && meta.touched", to avoid aggressive validation UX (https://vee-validate.logaretm.com/v4/guide/best-practices/#avoiding-aggressive-validation). - For TypeScript, wrap yup/zod/valibot schemas with
toTypedSchemafrom the matching@vee-validate/*package. Passing a raw schema without it fails with "No such validator 'VVTypedSchema' exists" (https://vee-validate.logaretm.com/v4/guide/composition-api/typed-schema/, https://github.com/logaretm/vee-validate/discussions/4819). useFieldinside a custom component must not sync its v-model by default (syncVModeldefaults tofalse, breaking change in 4.10.0). Opt in per field withsyncVModel: trueor a model prop name string (dist/vee-validate.mjs:1862).- Field names are paths. Dots nest objects,
[0]indexes arrays; wrap the name in brackets, e.g.[user.name], to treat dots as literal (https://vee-validate.logaretm.com/v4/guide/composition-api/nested-objects-and-arrays/). - The
errorsobject is always flat: reference the exact path string used as the field name, brackets included (https://vee-validate.logaretm.com/v4/guide/composition-api/nested-objects-and-arrays/). - Iterate array fields with
fieldsfromuseFieldArrayand keyv-forbyentry.key(a stable id, never the index) (https://vee-validate.logaretm.com/v4/guide/composition-api/nested-objects-and-arrays/). - Pass reactive field names as getters (
useField(() => props.name)) so vee-validate tracks name changes (https://vee-validate.logaretm.com/v4/guide/composition-api/caveats/). - Keep schemas non-reactive: declare them outside
ref/reactiveor wrap withmarkRawto avoid deep reactivity overhead (https://vee-validate.logaretm.com/v4/guide/best-practices/#reactive-schemas). handleSubmit.withControlled(cb)submits only fields registered withuseField/defineField(dist/vee-validate.d.ts:430-432); note typed schemas can still surface all initial values (open issue: https://github.com/logaretm/vee-validate/issues/4960).
Show full SKILL.md (118 more words)Show less
Validation modes
Global defaults: validateOnBlur: true, validateOnChange: true, validateOnInput: false, validateOnModelUpdate: true, bails: true. Change globally with configure(); note these four trigger flags only apply to the <Field> component, not useField (https://vee-validate.logaretm.com/v4/api/configuration/). To validate only on submit, disable input/change/blur triggers per field in defineField config or globally (https://github.com/logaretm/vee-validate/discussions/4903).
References
- Composition API:
useForm,defineField,useField,useFieldArray, state and setter composables, form context. - Components:
Form,Field,FieldArray,ErrorMessageprops, slots, rendering, v-model rules. - Validation: validator functions, object schemas, typed schemas, global rules, i18n, standalone
validateutils. - API surface: every runtime export and notable type, cited to
dist/vee-validate.d.ts. - Version changes: API additions, breaking changes, and deprecations from 4.9.0 to 4.15.1.
- Pitfalls: composition caveats, nested path rules, array fields, known open issues.
© skilld-dev, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 6 other files (references) in skills/vee-validate-skilld of skilld-dev/vue-ecosystem-skills.
- SKILL.md
- references/api-surface.md
- references/components.md
- references/composition-api.md
- references/pitfalls.md
- references/validation.md
- references/version-changes.md
Open the folder on GitHubat commit c8994af
Compare with similar skills
Vee Validate Skilld next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Vee Validate Skilld this skillskilld-dev/vue-ecosystem-skills | 181 | — | ~1.6k | Automated safety check: Pass | MIT | |
| Markbind Typescript MigrationMarkBind/markbind | 158 | — | ~2k | Automated safety check: Pass | MIT | |
| Releasedevlint/GitWand | 180 | — | ~1.8k | Automated safety check: Pass | MIT | |
| Cabloy Frontend Scaffoldcabloy/cabloy | 982 | — | ~4.1k | Automated safety check: Pass | MIT | |
| Nuxt Coresecondsky/claude-skills | 227 | — | ~3.4k | Automated safety check: Pass | MIT | |
| Vuetify Skilldlogue/vite-vuetify-ts-starter | 181 | 1 repos | ~1.9k | Automated safety check: Pass | MIT |
Similar skills
Release
devlint/GitWand
Guide a clean GitWand release end-to-end: bump version, update CHANGELOG, commit, tag, and push.
Cabloy Frontend Scaffold
cabloy/cabloy
A skill your agent uses whenever the user wants the Zova frontend path in this Cabloy repo: create or extend pages, components, api or model beans, route/query/params work, metadata refresh…
Nuxt Core
secondsky/claude-skills
| Nuxt 4 core framework fundamentals: project setup, configuration, routing, SEO, error handling, and directory structure.
Vuetify Skilld
logue/vite-vuetify-ts-starter
Vue Material Component Framework. An agent skill from logue/vite-vuetify-ts-starter.
Implement Ag Playbook
AgnosticUI/agnosticui
Implement a playbook from its PROMPT specification files. An agent skill from AgnosticUI/agnosticui.
More from skilld-dev/vue-ecosystem-skills
All 34 skills in this repoFloating UI Vue Skilld
skilld-dev/vue-ecosystem-skills
Floating UI for Vue (@floating-ui/vue@2.0.1). An agent skill from skilld-dev/vue-ecosystem-skills.
Formkit Core Skilld
skilld-dev/vue-ecosystem-skills
A skill your agent uses whenever writing, debugging, or reviewing code that imports @formkit/core — FormKit's framework-agnostic core (node trees, values, events, hooks, message stores, ledgers…
Pinia Colada Skilld
skilld-dev/vue-ecosystem-skills
Data fetching layer for Vue built on Pinia. An agent skill from skilld-dev/vue-ecosystem-skills.
Pinia Skilld
skilld-dev/vue-ecosystem-skills
A skill your agent uses when writing, debugging, or refactoring code that imports "pinia", the Vue 3 store library.
Primevue Skilld
skilld-dev/vue-ecosystem-skills
A skill your agent uses when writing, debugging, or updating code that imports primevue (PrimeVue v5, UI component library for Vue 3).
Quasar Skilld
skilld-dev/vue-ecosystem-skills
Build, configure, and debug apps with the Quasar framework (quasar npm package, v2.33.1).
Related
Categories
Questions about Vee Validate Skilld
What does Vee Validate Skilld do?
A skill your agent uses when writing, reviewing, or debugging Vue.js forms that import vee-validate (useForm, defineField, useField, useFieldArray, Form, Field, FieldArray, ErrorMessage). Vee Validate Skilld is an agent skill from skilld-dev/vue-ecosystem-skills.js forms that import vee-validate (useForm, defineField, useField, useFieldArray, Form, Field, FieldArray, ErrorMessage).
When should I use Vee Validate Skilld?
Vee Validate Skilld fits situations like: debugging Vue.js forms that import vee-validate (useForm.
How do I install Vee Validate Skilld in Claude Code?
Run `npx skills add skilld-dev/vue-ecosystem-skills --skill vee-validate-skilld -a claude-code`. Or copy the skill folder (skills/vee-validate-skilld in skilld-dev/vue-ecosystem-skills) into .claude/skills/vee-validate-skilld in your project. Claude Code loads it when a task matches its description.
How do I install Vee Validate Skilld in Codex?
Run `npx skills add skilld-dev/vue-ecosystem-skills --skill vee-validate-skilld -a codex`. Or copy the skill folder (skills/vee-validate-skilld in skilld-dev/vue-ecosystem-skills) into .agents/skills/vee-validate-skilld in your project. Codex loads it when a task matches its description.
Can I use Vee Validate Skilld in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add skilld-dev/vue-ecosystem-skills --skill vee-validate-skilld -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/vee-validate-skilld, .gemini/skills/vee-validate-skilld, .github/skills/vee-validate-skilld and .opencode/skills/vee-validate-skilld in your project.
What does Vee Validate Skilld need to run?
SKILL.md names no scripts, command-line tools or credentials: Vee Validate Skilld is instructions for the agent only.
Does Vee Validate Skilld access the network?
SKILL.md names 2 domains. As links in the text: vee-validate.logaretm.com and github.com. This is read from the text; nothing was executed.
Is Vee Validate Skilld safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Vee Validate Skilld use?
Vee Validate Skilld is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Vee Validate Skilld use?
About 1.6k tokens (SKILL.md is roughly 6.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 5.9k tokens, read only when the agent opens those files.
What are the alternatives to Vee Validate Skilld?
Skills that share tags, products or a category with Vee Validate Skilld: Markbind Typescript Migration (MarkBind/markbind, 158 stars), Release (devlint/GitWand, 180 stars), Cabloy Frontend Scaffold (cabloy/cabloy, 982 stars) and Nuxt Core (secondsky/claude-skills, 227 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Vee Validate Skilld?
skilld-dev (a GitHub organization) maintains it in skilld-dev/vue-ecosystem-skills, which has 181 GitHub stars. The repository holds 34 skills in this directory. The repository was last updated on September 22, 2026.
Source: skilld-dev/vue-ecosystem-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.