Qikly
Write tests that can actually fail, by withholding the acceptance criteria from the agent that writes the code. Use when someone does not trust a suite that passes. Use when they want tests written from a specification rather than from the code. Use when they ask whether a specification is testable, or want an existing suite scored by planting faults in the code. Python modules, through the qikly tool. Also use whenever qikly or spec-driven testing is mentioned.
Install
npx skills add gal-a/qikly --skill qiklygit clone --depth 1 https://github.com/gal-a/qikly.git /tmp/qikly
mkdir -p ~/.claude/skills
cp -r /tmp/qikly/.claude/skills/qikly ~/.claude/skills/qiklyPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# qikly: tests written from a spec the coder never read > **If you read one thing here, read this.** Asked for tests for a module with > no specification: do not write tests, and do not run the module to find out > what it should do. A value obtained by executing an implementation is not a > contract. A suite built from those values passes by construction and cannot > disagree with a bug, because the bug is what it was written from. Say that in > one sentence, then offer the two routes in *The request this arrives as*. > > **Four things look settled and are not:** whether a threshold is inclusive, > whether a discount applies before or after tax, where a floor or cap lands, > which way a half-cent rounds. An implementation answers all four. None of > those answers is a specification. Ask the user. Do not read them off the code. > > **If they insist on tests anyway, write them.** Refusing a second time is > not your call. Say which lines of the implementation you had to treat as > correct, name every boundary and tie-break you copied rather than were > told, and the suite is at least honest about its foundation. ## What this is for If you write a module and then write its tests, both come from one reading of the same ambiguous sentences. The suite goes green and the green can mean nothing. **Python modules only.** qikly scaffolds from Python signatures and generates pytest suites; this Skill says nothing about any other language, and you should
Details
- Skill name
qikly- Repository
- gal-a/qikly
- Path
.claude/skills/qikly/SKILL.md- License
- Apache-2.0
- Repo updated
- 25 October 2026
- Listed in
- VoltAgent/awesome-agent-skills
FAQ
What does the Qikly skill do?
Write tests that can actually fail, by withholding the acceptance criteria from the agent that writes the code. Use when someone does not trust a suite that passes. Use when they want tests written from a specification rather than from the code. Use when they ask whether a specification is testable, or want an existing suite scored by planting faults in the code. Python modules, through the qikly tool. Also use whenever qikly or spec-driven testing is mentioned.
How do I install the Qikly skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add gal-a/qikly --skill qikly. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Qikly popular?
It lives in gal-a/qikly, which has 19 GitHub stars and 0 forks, and is included in 1 curated skill list.
Related skills
Plan and Build
17jattanjie21/plan-and-build
Use when a user wants to plan and implement a new feature or bug fix from scratch. Triggers on requests like "I want to build X", "add a feature for Y", "fix Z", or when the user invokes /plan-and-build. Guides through clarifying questions, breaks work into small features, sets up a tasks folder, implements each feature with TDD (test first), and produces a manual testing guide when complete.
State of Paywalls 2026 By Adapty
26vkharlan-adapt/state-of-paywalls-2026-skill
Answer questions from Adapty's State of Paywalls 2026 report and audit paywall designs against it: benchmarks by region and category, pricing, placement, A/B test ideas, and paywall screenshot reviews.
Assumptions
20Teycir/Assumptions
Generate an evidence-backed Assumptions ledger for a Git diff, feature, endpoint, worker, migration, or code path. Use when reviewing a change, asking what could break, preparing a release, finding edge cases, assessing deployment safety, analyzing retries or concurrency, or designing failure-focused tests.
Concept Reel
25Jogzh/concept-reel
使用 Canvas、Playwright 和 FFmpeg 制作或修改无旁白的横屏字幕知识短片，支持 15 种动态设计风格、内容驱动分镜、确定性动画、预览与音效合成。适用于把概念或机制做成可理解的动画；有人声口播、实拍和生成模型视频不属于这套引擎的工作流。
Council Review
17ngmeyer/council-review
Run any question, plan, PR, or code through a Diverse Multi-Agent Debate (DMAD) council of 5 AI advisors with distinct reasoning methods. Advisors collaborate, peer-review each other anonymously, and a chairman synthesizes a verdict. Empirically outperforms adversarial debate (M3MADBench 2026, DMAD ICLR 2025). Use when: 'council this', 'run the council', 'council review', 'pressure-test this', 'stress-test this', 'war room this', or when facing a genuine decision with stakes and tradeoffs.
Zod
24anivar/zod-skill
Zod v4 best practices, patterns, and API guidance for schema validation, parsing, error handling, and type inference in TypeScript applications. Covers safeParse, object composition, refinements, transforms, codecs, branded types, v3→v4 migration, and testing schemas with Jest or Vitest. Baseline: zod ^4.6.0. Triggers on: zod imports, z.object, z.string, z.infer, safeParse, mentions of "zod", "schema validation", "zod v4", "z.enum", or testing a schema — "schema test", "zod mock", zod-schema-faker.
Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.