Verify
lkmeta/txtify
Verify a Txtify change end-to-end. An agent skill from lkmeta/txtify.
Convert messy voice input, imperfect speech recognition, half-formed product ideas, and iterative corrections into an implementation-ready software specification for Codex, Claude Code, Copilot…
Install Vibe To Spec
$ npx skills add FAIRY123456789/human-edge-agent-skills --skill vibe-to-spec -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install FAIRY123456789/human-edge-agent-skills vibe-to-spec --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/FAIRY123456789/human-edge-agent-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/vibe-to-spec .claude/skills/vibe-to-spec && 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 "vibe-to-spec" agent skill from https://github.com/FAIRY123456789/human-edge-agent-skills/tree/main/skills/vibe-to-spec into .claude/skills/vibe-to-spec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vibe-to-spec", 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/FAIRY123456789/human-edge-agent-skills/tree/main/skills/vibe-to-specType 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 FAIRY123456789/human-edge-agent-skills --skill vibe-to-spec -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install FAIRY123456789/human-edge-agent-skills vibe-to-spec --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/FAIRY123456789/human-edge-agent-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/vibe-to-spec .agents/skills/vibe-to-spec && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "vibe-to-spec" agent skill from https://github.com/FAIRY123456789/human-edge-agent-skills/tree/main/skills/vibe-to-spec into .agents/skills/vibe-to-spec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vibe-to-spec", 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 FAIRY123456789/human-edge-agent-skills --skill vibe-to-spec -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install FAIRY123456789/human-edge-agent-skills vibe-to-spec --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/FAIRY123456789/human-edge-agent-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/vibe-to-spec .cursor/skills/vibe-to-spec && 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 "vibe-to-spec" agent skill from https://github.com/FAIRY123456789/human-edge-agent-skills/tree/main/skills/vibe-to-spec into .cursor/skills/vibe-to-spec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vibe-to-spec", 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/FAIRY123456789/human-edge-agent-skills.git --path skills/vibe-to-spec--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 FAIRY123456789/human-edge-agent-skills --skill vibe-to-spec -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install FAIRY123456789/human-edge-agent-skills vibe-to-spec --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/FAIRY123456789/human-edge-agent-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/vibe-to-spec .gemini/skills/vibe-to-spec && 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 "vibe-to-spec" agent skill from https://github.com/FAIRY123456789/human-edge-agent-skills/tree/main/skills/vibe-to-spec into .gemini/skills/vibe-to-spec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vibe-to-spec", 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 FAIRY123456789/human-edge-agent-skills vibe-to-specInstalls 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 FAIRY123456789/human-edge-agent-skills --skill vibe-to-spec -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/FAIRY123456789/human-edge-agent-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/vibe-to-spec .github/skills/vibe-to-spec && 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 "vibe-to-spec" agent skill from https://github.com/FAIRY123456789/human-edge-agent-skills/tree/main/skills/vibe-to-spec into .github/skills/vibe-to-spec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vibe-to-spec", 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 FAIRY123456789/human-edge-agent-skills --skill vibe-to-spec -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install FAIRY123456789/human-edge-agent-skills vibe-to-spec --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/FAIRY123456789/human-edge-agent-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/vibe-to-spec .opencode/skills/vibe-to-spec && 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 "vibe-to-spec" agent skill from https://github.com/FAIRY123456789/human-edge-agent-skills/tree/main/skills/vibe-to-spec into .opencode/skills/vibe-to-spec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vibe-to-spec", 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
vibe-to-spec- GitHub stars
- 103
- Token cost
- ~997 tokens
- SKILL.md length
- 424 words
- Files
- 4 (incl. references, assets)
- Skills in repo
- 18
- Repo updated
- First seen
- Licence
- MIT
At a glance
Convert messy voice input, imperfect speech recognition, half-formed product ideas, and iterative corrections into an implementation-ready software specification for Codex, Claude Code, Copilot…
- Works in 10 steps: Read the entire voice dump before… → Build an active glossary from → Resolve suspicious ASR terms with… → …
- The user speaks faster than they structure requirements
- SKILL.md covers Purpose, This skill is not…, Instructions and Output, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Vibe To Spec is an agent skill from FAIRY123456789/human-edge-agent-skills. Convert messy voice input, imperfect speech recognition, half-formed product ideas, and iterative corrections into an implementation-ready software specification for Codex, Claude Code, Copilot, Cursor, or another coding agent. Use when the user speaks faster than they structure requirements, named entities are misrecognized, context or memory can safely resolve recurring terms, and the final output needs scope, flows, data, constraints, acceptance tests, and explicit unknowns rather than a raw transcript.
Its SKILL.md is about 1000 tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including reference files and assets (for example `README.md`, `assets/SPEC_TEMPLATE.md` and `references/asr-context-resolution.md`).
It sits in AI & LLM Engineering, covering Speech recognition and synthesis and End-to-end testing. The repository describes itself as: 18 portable Agent Skills for voice-native AI, human judgment, microbets, social tact, writing, life systems, and safe deployment. The licence is MIT.
When your agent uses it
- The user speaks faster than they structure requirements
- Named entities are misrecognized
- Memory can safely resolve recurring terms
- The final output needs scope
Example prompts
- “/vibe-to-spec”
Workflow steps
10 steps, taken from the first numbered list in SKILL.md.
- Read the entire voice dump before normalizing anything. Later sentences often correct earlier ASR errors or change scope.
- Build an active glossary from
- Resolve suspicious ASR terms with references/asr-context-resolution.md.
- Maintain a correction ledger for meaningful corrections. High-confidence corrections can be normalized silently in the spec…
- Recover intent in layers
- Convert subjective language into testable behavior. “更好看” needs design direction or reference; “更快” needs a measurable threshold or a…
- Preserve the user's corrections and vetoes. Later explicit corrections override earlier inferred intent.
- Do not ask questions that the context can already answer. Ask only when ambiguity changes architecture, data loss risk, cost, security, or…
- Produce the implementation pack using assets/SPEC_TEMPLATE.md.
- End with a Ready for coding agent status: YES, YES_WITH_ASSUMPTIONS, or NO_BLOCKED.
What it can do on your machine
Read from SKILL.md and the folder at commit 31a0a16. 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.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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
Vibe To Spec loads about 997 tokens when it runs, and up to ~1.4k if it reads all its reference files. Until then it costs about 131 tokens; SKILL.md has 424 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 FAIRY123456789/human-edge-agent-skills at commit 31a0a16, republished under its MIT licence (© FAIRY123456789). 424 words, ~997 tokens.
Download SKILL.mdSave it as
.claude/skills/vibe-to-spec/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.- name
- vibe-to-spec
- description
- Convert messy voice input, imperfect speech recognition, half-formed product ideas, and iterative corrections into an implementation-ready software specification for Codex, Claude Code, Copilot, Cursor, or another coding agent. Use when the user speaks faster than they structure requirements, named entities are misrecognized, context or memory can safely resolve recurring terms, and the final output needs scope, flows, data, constraints, acceptance tests, and explicit unknowns rather than a raw transcript.
- license
- MIT
- metadata.author
- Joy T <101039451+FAIRY123456789@users.noreply.github.com>
- metadata.tags
- specifications, voice-input, software-development
Vibe to Spec
Purpose
The user's speech can be fuzzy. The implementation contract cannot be. Recover intent without hiding consequential uncertainty or inventing remembered context.
This skill is not voice-dump-to-todo
Use vibe-to-spec when the destination is a product, feature, code change, system, webpage, API, or technical build.
Use voice-dump-to-todo when the destination is the user's personal execution list: tasks, decisions, waiting items, deadlines, and an interactive to-do.
Instructions
- Read the entire voice dump before normalizing anything. Later sentences often correct earlier ASR errors or change scope.
- Build an active glossary from:
- exact terms repeated in the current input;
- named entities in the active conversation or project context;
- user-provided glossaries or files;
- host-provided memory only when the product legitimately exposes it and the user would reasonably expect it to be used.
- Resolve suspicious ASR terms with
references/asr-context-resolution.md. - Maintain a correction ledger for meaningful corrections. High-confidence corrections can be normalized silently in the spec; medium-confidence corrections must remain visible as assumptions; low-confidence terms remain unresolved.
- Recover intent in layers:
- goal and target user;
- current problem;
- in-scope behaviors;
- explicit out-of-scope items;
- user flow;
- screens and components;
- data and entities;
- integrations and APIs;
- constraints and non-negotiables;
- acceptance tests;
- open questions that genuinely block implementation.
- Convert subjective language into testable behavior. “更好看” needs design direction or reference; “更快” needs a measurable threshold or a marked unknown.
- Preserve the user's corrections and vetoes. Later explicit corrections override earlier inferred intent.
- Do not ask questions that the context can already answer. Ask only when ambiguity changes architecture, data loss risk, cost, security, or acceptance.
- Produce the implementation pack using
assets/SPEC_TEMPLATE.md. - End with a
Ready for coding agentstatus:YES,YES_WITH_ASSUMPTIONS, orNO_BLOCKED.
Show full SKILL.md (139 more words)Show less
Output
Default deliverable:
- normalized brief;
- correction ledger for non-trivial ASR fixes;
- implementation specification content;
- acceptance criteria;
- assumptions and open blockers;
- suggested implementation order.
Never invent a remembered project name merely because it sounds plausible.
Examples
- Input: a voice transcript that first says “mobile page,” later corrects it to a responsive web dashboard, and leaves the export format uncertain.
- Output: the corrected scope, a visible export-format assumption, user flows, data entities, acceptance tests, and
YES_WITH_ASSUMPTIONSreadiness.
Limitations
Do not resolve names from memory when the host does not legitimately expose that context. Do not mark a specification ready when ambiguity changes architecture, cost, security, or data-loss risk.
Troubleshooting
If corrections conflict, prefer the latest explicit correction and record the conflict. If the requested behavior cannot be tested, rewrite it as an observable outcome or leave it as an open blocker.
© FAIRY123456789, 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 3 other files (references, assets) in skills/vibe-to-spec of FAIRY123456789/human-edge-agent-skills.
- SKILL.md
- README.md
- assets/SPEC_TEMPLATE.md
- references/asr-context-resolution.md
Open the folder on GitHubat commit 31a0a16
Compare with similar skills
Vibe To Spec 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 |
|---|---|---|---|---|---|---|
| Vibe To Spec this skillFAIRY123456789/human-edge-agent-skills | 103 | — | ~997 | Automated safety check: Pass | MIT | |
| Verifylkmeta/txtify | 135 | — | ~583 | Automated safety check: Pass | Apache-2.0 | |
| Paperclip Evalspaperclipai/paperclip | 100k | — | ~839 | Automated safety check: Pass | MIT | |
| Developing Changerapidaai/voice-ai | 745 | — | ~661 | Automated safety check: Pass | Custom licence | |
| Digital Health Clinical Asr SetupNVIDIA/skills | 3.6k | — | ~4.5k | Automated safety check: Notes | Apache-2.0 | |
| TriageTalAter/annyang | 6.8k | — | ~810 | Automated safety check: Notes | MIT |
Similar skills
Paperclip Evals
paperclipai/paperclip
Choose, inspect, validate, and report Paperclip Runner or Product E2E evaluations while preserving evidence, provenance, cost, and failure classification.
Developing Change
rapidaai/voice-ai
Implement an approved repository change with explicit ownership, minimal scope, test-first evidence, and scoped verification.
- Official
Digital Health Clinical Asr Setup
NVIDIA/skills
Stage 1 of Clinical ASR Flywheel. An agent skill from NVIDIA/skills.
Triage
TalAter/annyang
Triage and close GitHub issues on TalAter/annyang. An agent skill from TalAter/annyang.
Yichen Asr
mcncarl/yichen-skills
逸尘自用的统一音视频转写入口，在 StepFun Step ASR 与火山引擎豆包 ASR 之间按输出需求、安全边界和可用状态路由。用于本地音频或视频的纯文本转写、时间戳、SRT 字幕、口播粗剪，以及转写前体检；用户明确指定服务商时不得静默切换。Use when a local audio or video file needs transcription and the correct…
More from FAIRY123456789/human-edge-agent-skills
All 18 skills in this repoAliyun Fullstack Deploy
FAIRY123456789/human-edge-agent-skills
Deploy full-stack apps to user-authorized Alibaba Cloud ECS or comparable Linux VPS hosts with preflight, canary verification, and rollback.
Skill From Scars
FAIRY123456789/human-edge-agent-skills
Mine repeated pain from transcripts, project retrospectives, debugging logs, failed prompts, deployment notes, or work history and decide whether it deserves to become a reusable Agent Skill.
Voice Dump To Todo
FAIRY123456789/human-edge-agent-skills
Convert a long, messy, repetitive, speech-recognition-heavy task dump into a precise executable to-do list.
Deployment Proof
FAIRY123456789/human-edge-agent-skills
Convert deployment logs, validation reports, Git history, and comparison notes into a redacted GitHub case study, portfolio entry, interview story, and evidence-backed resume bullets.
Build In Public Launcher
FAIRY123456789/human-edge-agent-skills
Turn a finished or nearly finished Skill, plugin, repository, micro-tool, research utility, or AI project into a credible public launch that can earn real users and feedback.
Small Server Fit
FAIRY123456789/human-edge-agent-skills
Assess whether a web application and its build and runtime plan fit a low-cost Linux VPS or Alibaba Cloud ECS before purchase, implementation, or deployment.
Related
Categories
Questions about Vibe To Spec
What does Vibe To Spec do?
Convert messy voice input, imperfect speech recognition, half-formed product ideas, and iterative corrections into an implementation-ready software specification for Codex, Claude Code, Copilot…. Vibe To Spec is an agent skill from FAIRY123456789/human-edge-agent-skills. Convert messy voice input, imperfect speech recognition, half-formed product ideas, and iterative corrections into an implementation-ready software specification for Codex, Claude Code, Copilot, Cursor, or another coding agent.
When should I use Vibe To Spec?
Vibe To Spec fits situations like: the user speaks faster than they structure requirements; named entities are misrecognized; memory can safely resolve recurring terms; the final output needs scope.
How do I install Vibe To Spec in Claude Code?
Run `npx skills add FAIRY123456789/human-edge-agent-skills --skill vibe-to-spec -a claude-code`. Or copy the skill folder (skills/vibe-to-spec in FAIRY123456789/human-edge-agent-skills) into .claude/skills/vibe-to-spec in your project. Claude Code loads it when a task matches its description.
How do I install Vibe To Spec in Codex?
Run `npx skills add FAIRY123456789/human-edge-agent-skills --skill vibe-to-spec -a codex`. Or copy the skill folder (skills/vibe-to-spec in FAIRY123456789/human-edge-agent-skills) into .agents/skills/vibe-to-spec in your project. Codex loads it when a task matches its description.
Can I use Vibe To Spec 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 FAIRY123456789/human-edge-agent-skills --skill vibe-to-spec -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/vibe-to-spec, .gemini/skills/vibe-to-spec, .github/skills/vibe-to-spec and .opencode/skills/vibe-to-spec in your project.
What does Vibe To Spec need to run?
SKILL.md names no scripts, command-line tools or credentials: Vibe To Spec is instructions for the agent only.
Does Vibe To Spec access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Vibe To Spec 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 Vibe To Spec use?
Vibe To Spec is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Vibe To Spec use?
About 997 tokens (SKILL.md is roughly 4k 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 392 tokens, read only when the agent opens those files.
What are the alternatives to Vibe To Spec?
Skills that share tags, products or a category with Vibe To Spec: Verify (lkmeta/txtify, 135 stars), Paperclip Evals (paperclipai/paperclip, 100k stars), Developing Change (rapidaai/voice-ai, 745 stars) and Digital Health Clinical Asr Setup (NVIDIA/skills, 3.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Vibe To Spec?
FAIRY123456789 (a GitHub user) maintains it in FAIRY123456789/human-edge-agent-skills, which has 103 GitHub stars. The repository holds 18 skills in this directory. The repository was last updated on October 10, 2026.
Source: FAIRY123456789/human-edge-agent-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.