Plugin Test
apache/skywalking-python
Build Docker test images and run SkyWalking Python plugin/unit/e2e tests locally, mirroring the CI pipeline
Verify a Txtify change end-to-end. An agent skill from lkmeta/txtify.
Install Verify
$ npx skills add lkmeta/txtify --skill verify -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install lkmeta/txtify verify --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/lkmeta/txtify.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/verify .claude/skills/verify && 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 "verify" agent skill from https://github.com/lkmeta/txtify/tree/main/.claude/skills/verify into .claude/skills/verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verify", 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/lkmeta/txtify/tree/main/.claude/skills/verifyType 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 lkmeta/txtify --skill verify -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install lkmeta/txtify verify --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/lkmeta/txtify.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/verify .agents/skills/verify && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "verify" agent skill from https://github.com/lkmeta/txtify/tree/main/.claude/skills/verify into .agents/skills/verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verify", 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 lkmeta/txtify --skill verify -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install lkmeta/txtify verify --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/lkmeta/txtify.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/verify .cursor/skills/verify && 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 "verify" agent skill from https://github.com/lkmeta/txtify/tree/main/.claude/skills/verify into .cursor/skills/verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verify", 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/lkmeta/txtify.git --path .claude/skills/verify--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 lkmeta/txtify --skill verify -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install lkmeta/txtify verify --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/lkmeta/txtify.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/verify .gemini/skills/verify && 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 "verify" agent skill from https://github.com/lkmeta/txtify/tree/main/.claude/skills/verify into .gemini/skills/verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verify", 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 lkmeta/txtify verifyInstalls 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 lkmeta/txtify --skill verify -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/lkmeta/txtify.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/verify .github/skills/verify && 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 "verify" agent skill from https://github.com/lkmeta/txtify/tree/main/.claude/skills/verify into .github/skills/verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verify", 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 lkmeta/txtify --skill verify -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install lkmeta/txtify verify --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/lkmeta/txtify.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/verify .opencode/skills/verify && 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 "verify" agent skill from https://github.com/lkmeta/txtify/tree/main/.claude/skills/verify into .opencode/skills/verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verify", 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
verify- GitHub stars
- 135
- Token cost
- ~583 tokens
- SKILL.md length
- 259 words
- Files
- 1
- Skills in repo
- 2
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Verify a Txtify change end-to-end. An agent skill from lkmeta/txtify.
- Tasks that involve Containers
- SKILL.md covers Tier 1 — unit/API tests…, Tier 2 — Docker E2E (the real…, Reading failures and What "verified" means in a PR…
- Calls docker, pytest and pip
- Tasks that involve Transcription
What it does
Verify is an agent skill from lkmeta/txtify. Verify a Txtify change end-to-end. Use before committing any nontrivial change, when asked to "verify", "test this", or "make sure nothing breaks", and always after touching the worker/transcription path, dependencies, or the Dockerfile.
Its SKILL.md is about 580 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in DevOps & Cloud, covering Containers, Transcription and End-to-end testing. It works with Docker, Python and FastAPI. The repository describes itself as: Web application that converts audio and video to text using AI, supporting various formats and self-hosting. The licence is Apache-2.0.
When your agent uses it
- Tasks that involve Containers
- Tasks that involve Transcription
- Tasks that involve End-to-end testing
Example prompts
- “verify”
- “test this”
- “make sure nothing breaks”
- “/verify”
Requirements
- Python 3
- Docker
What it can do on your machine
Read from SKILL.md and the folder at commit b54c884. 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
Shell commands in SKILL.md call:
dockerpytestpip
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use docker and pip, which can reach the network depending on how they are called.
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
Verify loads about 583 tokens when it runs. Until then it costs about 61 tokens; SKILL.md has 259 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 lkmeta/txtify at commit b54c884, republished under its Apache-2.0 licence (© lkmeta). 259 words, ~583 tokens.
Download SKILL.mdSave it as
.claude/skills/verify/SKILL.md (or your agent's skills folder).- name
- verify
- description
- Verify a Txtify change end-to-end. Use before committing any nontrivial change, when asked to "verify", "test this", or "make sure nothing breaks", and always after touching the worker/transcription path, dependencies, or the Dockerfile.
Verifying Txtify changes
Two tiers. Pick the cheapest one that actually exercises the change.
Tier 1 — unit/API tests (seconds, no ML stack needed)
pytest -qCovers: format converters (incl. PDF Unicode round-trip), filename/URL/upload validation, job-id DB flow, /health, /transcribe error paths, DeepL alignment edge cases. tests/conftest.py stubs torch/stable_whisper when absent, so a light venv is enough:
grep -v -E '^(torch|stable-ts)' requirements.txt > /tmp/reqs.txt
pip install -r /tmp/reqs.txt pytest httpx pypdfSufficient on its own only for changes fully covered by tests (converters, validation, endpoint logic).
Tier 2 — Docker E2E (the real gate, ~5–10 min)
./scripts/docker_e2e.shBuilds the image, boots a container, checks /health + all pages + 404s, uploads a generated clip, runs a real whisper-tiny transcription to 100%, validates preview in all four formats, downloads the zip and confirms the PDF is in it, and checks validation errors. Success is the literal line PASS: docker E2E complete.
Mandatory for changes to: requirements.txt, Dockerfile, .dockerignore, src/transcribe_process.py, src/models.py, the worker-spawn path in src/utils.py.
Reading failures
- Status stuck at 10% → worker crashed at import (classic cause: torch/torchaudio version mismatch). Reproduce inside the container:
docker exec <name> python /app/src/transcribe_process.py 99 output/<clip> en whisper_tiny none en all - Status stuck at 30% for a long time → model download in progress; not a failure yet.
- Job errors mid-run →
docker exec <name> cat output/<job id>_logs.txt(the server log won't show worker errors). - The E2E script's container is removed on exit; to debug interactively,
docker run -d --rm --name txtify_dbg -p 8078:8011 txtify:e2eand drive it with curl.
What "verified" means in a PR body
Paste the actual output: the pytest summary line and/or the PASS: docker E2E complete line. A claim without output doesn't count.
© lkmeta, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .claude/skills/verify of lkmeta/txtify.
Open the folder on GitHubat commit b54c884
Compare with similar skills
Verify 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 |
|---|---|---|---|---|---|---|
| Verify this skilllkmeta/txtify | 135 | — | ~583 | Automated safety check: Pass | Apache-2.0 | |
| Plugin Testapache/skywalking-python | 219 | — | ~2.3k | Automated safety check: Pass | Apache-2.0 | |
| Acarshub Tool Additionssdr-enthusiasts/docker-acarshub | 117 | — | ~707 | Automated safety check: Pass | GPL-3.0 | |
| Make Python Recipe Deployablegoogle/adk-recipes | 10k | — | ~6.9k | Automated safety check: Notes | Apache-2.0 | |
| Cosmos3 Env TroubleshootNVIDIA/cosmos-framework | 558 | — | ~1.3k | Automated safety check: Notes | Custom licence | |
| Generate Nemo Gym Envadithya-s-k/FineEnvs | 443 | — | ~2.1k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Acarshub Tool Additions
sdr-enthusiasts/docker-acarshub
Use ONLY when working in the docker-acarshub repository AND a task may require adding a system tool, npm package, or other dependency.
- Official
Make Python Recipe Deployable
google/adk-recipes
Makes an existing Python recipe deployable: generates the serving files a container needs (Dockerfile, .dockerignore, fastapiapp.py, apputils/a2a.py, apputils/services.py…
- Official
Cosmos3 Env Troubleshoot
NVIDIA/cosmos-framework
Diagnose and fix Cosmos3 environment, installation, and runtime errors.
Generate Nemo Gym Env
adithya-s-k/FineEnvs
Builds a NeMo Gym (NVIDIA) variant of an RL environment. An agent skill from adithya-s-k/FineEnvs.
Generate Ors Env
adithya-s-k/FineEnvs
Builds an Open Reward Standard (ORS) variant of an RL environment using the official openreward Python package.
More from lkmeta/txtify
Deps Bump
lkmeta/txtify
Safely update Txtify dependencies or resolve Dependabot alerts.
Related
Questions about Verify
What does Verify do?
Verify a Txtify change end-to-end. An agent skill from lkmeta/txtify. Verify is an agent skill from lkmeta/txtify. Verify a Txtify change end-to-end.
When should I use Verify?
Verify fits situations like: tasks that involve Containers; tasks that involve Transcription; tasks that involve End-to-end testing.
How do I install Verify in Claude Code?
Run `npx skills add lkmeta/txtify --skill verify -a claude-code`. Or copy the skill folder (.claude/skills/verify in lkmeta/txtify) into .claude/skills/verify in your project. Claude Code loads it when a task matches its description.
How do I install Verify in Codex?
Run `npx skills add lkmeta/txtify --skill verify -a codex`. Or copy the skill folder (.claude/skills/verify in lkmeta/txtify) into .agents/skills/verify in your project. Codex loads it when a task matches its description.
Can I use Verify 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 lkmeta/txtify --skill verify -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/verify, .gemini/skills/verify, .github/skills/verify and .opencode/skills/verify in your project.
What does Verify need to run?
Going by SKILL.md and its folder, Verify needs the command-line tools its instructions call (docker, pytest and pip). Our summary lists: Python 3; Docker.
Does Verify access the network?
SKILL.md contains no URLs. Its commands use docker and pip, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Verify 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 Verify use?
Verify is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Verify use?
About 583 tokens (SKILL.md is roughly 2.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Verify?
Skills that share tags, products or a category with Verify: Plugin Test (apache/skywalking-python, 219 stars), Acarshub Tool Additions (sdr-enthusiasts/docker-acarshub, 117 stars), Make Python Recipe Deployable (google/adk-recipes, 10k stars) and Cosmos3 Env Troubleshoot (NVIDIA/cosmos-framework, 558 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Verify?
lkmeta (a GitHub user) maintains it in lkmeta/txtify, which has 135 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on August 15, 2026.
Source: lkmeta/txtify on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.