Add Redis Command to go-redis
redis/go-redis
Walks through adding a new Redis or Redis module command to the go-redis client, from fetching the spec and docs to the type, interface wiring, parsing and tests.
Add or refactor a specx core scope use case. An agent skill from maksimzayats/specx.
Install Specx Add Core Use Case
$ npx skills add maksimzayats/specx --skill specx-add-core-use-case -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install maksimzayats/specx specx-add-core-use-case --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/maksimzayats/specx.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/specx-add-core-use-case .claude/skills/specx-add-core-use-case && 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 "specx-add-core-use-case" agent skill from https://github.com/maksimzayats/specx/tree/main/skills/specx-add-core-use-case into .claude/skills/specx-add-core-use-case/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "specx-add-core-use-case", 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/maksimzayats/specx/tree/main/skills/specx-add-core-use-caseType 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 maksimzayats/specx --skill specx-add-core-use-case -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install maksimzayats/specx specx-add-core-use-case --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/maksimzayats/specx.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/specx-add-core-use-case .agents/skills/specx-add-core-use-case && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "specx-add-core-use-case" agent skill from https://github.com/maksimzayats/specx/tree/main/skills/specx-add-core-use-case into .agents/skills/specx-add-core-use-case/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "specx-add-core-use-case", 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 maksimzayats/specx --skill specx-add-core-use-case -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install maksimzayats/specx specx-add-core-use-case --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/maksimzayats/specx.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/specx-add-core-use-case .cursor/skills/specx-add-core-use-case && 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 "specx-add-core-use-case" agent skill from https://github.com/maksimzayats/specx/tree/main/skills/specx-add-core-use-case into .cursor/skills/specx-add-core-use-case/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "specx-add-core-use-case", 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/maksimzayats/specx.git --path skills/specx-add-core-use-case--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 maksimzayats/specx --skill specx-add-core-use-case -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install maksimzayats/specx specx-add-core-use-case --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/maksimzayats/specx.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/specx-add-core-use-case .gemini/skills/specx-add-core-use-case && 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 "specx-add-core-use-case" agent skill from https://github.com/maksimzayats/specx/tree/main/skills/specx-add-core-use-case into .gemini/skills/specx-add-core-use-case/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "specx-add-core-use-case", 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 maksimzayats/specx specx-add-core-use-caseInstalls 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 maksimzayats/specx --skill specx-add-core-use-case -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/maksimzayats/specx.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/specx-add-core-use-case .github/skills/specx-add-core-use-case && 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 "specx-add-core-use-case" agent skill from https://github.com/maksimzayats/specx/tree/main/skills/specx-add-core-use-case into .github/skills/specx-add-core-use-case/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "specx-add-core-use-case", 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 maksimzayats/specx --skill specx-add-core-use-case -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install maksimzayats/specx specx-add-core-use-case --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/maksimzayats/specx.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/specx-add-core-use-case .opencode/skills/specx-add-core-use-case && 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 "specx-add-core-use-case" agent skill from https://github.com/maksimzayats/specx/tree/main/skills/specx-add-core-use-case into .opencode/skills/specx-add-core-use-case/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "specx-add-core-use-case", 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
specx-add-core-use-case- GitHub stars
- 202
- Token cost
- ~1.1k tokens
- SKILL.md length
- 491 words
- Files
- 3 (incl. references)
- Skills in repo
- 12
- Repo updated
- First seen
- Licence
- MIT
At a glance
Add or refactor a specx core scope use case. An agent skill from maksimzayats/specx.
- Works in 11 steps: Name the action directly, for example… → Put it under core//use_cases/.py. → Inherit BaseUseCase from… → …
- Implementing an externally meaningful application action under a core scope usecases package
- SKILL.md covers Workflow, Transaction Rule, Code Style and References
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Specx Add Core Use Case is an agent skill from maksimzayats/specx. Add or refactor a specx core scope use case. Use when implementing an externally meaningful application action under a core scope usecases package, adding same-file command/query inputs, result DTOs, coordinating services, opening a unit-of-work transaction, or moving behavior out of delivery or infrastructure into class-based application code.
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `agents/openai.yaml` and `references/use-case.md`).
It sits in Development. The repository describes itself as: ⚙️ Executable architecture guardrails and agent skills for building structured Python services! The licence is MIT.
When your agent uses it
- Implementing an externally meaningful application action under a core scope usecases package
- Adding same-file command/query inputs
- Coordinating services
- Opening a unit-of-work transaction
Example prompts
- “/specx-add-core-use-case”
Workflow steps
11 steps, taken from the first numbered list in SKILL.md.
- Name the action directly, for example CreateInvoiceUseCase.
- Put it under core//use_cases/.py.
- Inherit BaseUseCase from specx.core.foundation.use_case.
- Define exactly one same-file input class: a Command for state-changing
- Make commands inherit specx.core.foundation.command.BaseCommand, queries inherit
- Treat commands and queries as input contracts, not DTOs. Do not make
- execute(...) accepts exactly one keyword-only argument named command or
- Inject services, capabilities, gateways, and UoW managers with
- Keep framework schemas, routers, ORM models, Redis clients, HTTP clients,
- Mark secret-bearing dataclass fields with field(repr=False) and never log
- Add or update flat unit tests for the behavior. The test receives the
What it can do on your machine
Read from SKILL.md and the folder at commit 9362406. 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
Specx Add Core Use Case loads about 1.1k tokens when it runs, and up to ~4.6k if it reads all its reference files. Until then it costs about 93 tokens; SKILL.md has 491 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 maksimzayats/specx at commit 9362406, republished under its MIT licence (© maksimzayats). 491 words, ~1,052 tokens.
Download SKILL.mdSave it as
.claude/skills/specx-add-core-use-case/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.- name
- specx-add-core-use-case
- description
- Add or refactor a specx core scope use case. Use when implementing an externally meaningful application action under a core scope use_cases package, adding same-file command/query inputs, result DTOs, coordinating services, opening a unit-of-work transaction, or moving behavior out of delivery or infrastructure into class-based application code.
specx Add Core Use Case
Use this skill for one application action at a time. Read
references/use-case.md before writing the use case.
Workflow
- Name the action directly, for example
CreateInvoiceUseCase. - Put it under
core/<scope>/use_cases/<action>.py. - Inherit
BaseUseCasefromspecx.core.foundation.use_case. - Define exactly one same-file input class: a
Commandfor state-changing use cases or aQueryfor read-only use cases. Even empty inputs are explicit. - Make commands inherit
specx.core.foundation.command.BaseCommand, queries inheritspecx.core.foundation.query.BaseQuery, and result DTOs inheritspecx.core.foundation.dto.BaseDTO. Prefer@dataclass(frozen=True, kw_only=True, slots=True)for all of these core data classes unless the user asks for another model type. - Treat commands and queries as input contracts, not DTOs. Do not make
commands or queries inherit
BaseDTO, put them underdtos/, or add aDTOsuffix. execute(...)accepts exactly one keyword-only argument namedcommandorqueryand returns DTOs, not entities.- Inject services, capabilities, gateways, and UoW managers with
Injected[...]. Keep infrastructure/runtime settings out of core use cases; expose required business policy as a typed core value or collaborator. For transactional persistence, inject the scopeUnitOfWorkManagerand open the active unit of work insideexecute(...). Do not inject repositories, SQLAlchemy sessions/engines/session factories, or concrete infrastructure adapters directly into use cases. - Keep framework schemas, routers, ORM models, Redis clients, HTTP clients, and entity return types out of the use case.
- Mark secret-bearing dataclass fields with
field(repr=False)and never log whole commands, queries, or DTOs that may contain sensitive values. - Add or update flat unit tests for the behavior. The test receives the
native pytest
containerfixture, registers local doubles or inline mocks before resolution, and resolves the use case withcontainer.resolve(UseCaseClass). If the use case injects aUnitOfWorkManager, also add a core integration test undertests/integration/core/...against the real persistence graph (and the transactional database graph when database-backed).
CheckReadinessUseCase may live under core/health when readiness checks any
required external dependency or multiple delivery layers reuse the policy. Add
a core CheckLivenessUseCase only when framework-independent liveness policy
is genuinely reused across deliveries; keep a simple process-only liveness
response in delivery. HTTP paths, status codes, headers, and schemas always
stay in delivery.
Show full SKILL.md (138 more words)Show less
Transaction Rule
A use case may open one unit-of-work scope inside execute(...) when database
work is part of the action. Inject the manager, not Provider[UnitOfWork] and
not an active UoW instance, repository, SQLAlchemy session/engine/session
factory, or concrete infrastructure adapter. Read/effect services may receive
the active unit_of_work, but services do not open transactions. Repository
calls from a use case stay rooted in the manager-owned unit_of_work variable.
Commands are allowed to change state. Queries are read-only and should not call
repository mutators such as add, save, create, update, or delete, or
invoke gateways with external write effects.
Code Style
Use blank lines as logical separators in all code. Keep related statements together, but separate independent setup, action, assertion, response, branch, and transformation groups so long blocks stay readable.
References
references/use-case.md- use-case class shape, DTO examples, UoW examples, and test guidance.
© maksimzayats, 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 2 other files (references) in skills/specx-add-core-use-case of maksimzayats/specx.
- SKILL.md
- agents/openai.yaml
- references/use-case.md
Open the folder on GitHubat commit 9362406
Compare with similar skills
Specx Add Core Use Case 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 |
|---|---|---|---|---|---|---|
| Specx Add Core Use Case this skillmaksimzayats/specx | 202 | — | ~1.1k | Automated safety check: Pass | MIT | |
| Add Redis Command to go-redisredis/go-redis | 22k | — | ~1.4k | Automated safety check: Pass | BSD-2-Clause | |
| Citus Merge Loopcitusdata/citus | 13k | — | ~2.5k | Automated safety check: Pass | AGPL-3.0 | |
| YugabyteDB ASH Instrumentationyugabyte/yugabyte-db | 11k | — | ~4.5k | Automated safety check: Pass | Custom licence | |
| SeekDB Code Reviewoceanbase/seekdb | 3.1k | — | ~2.1k | Automated safety check: Pass | Apache-2.0 | |
| Add Garnet RESP Commandmicrosoft/garnet | 12k | — | ~9.7k | Automated safety check: Pass | MIT |
Similar skills
- Official
Citus Merge Loop
citusdata/citus
Take a list of citusdata/citus PR links or numbers and merge each one independently: sync it with its base branch, fix a red check-style job with make reindent, retry other red checks a bounded…
YugabyteDB ASH Instrumentation
yugabyte/yugabyte-db
Procedure for adding or changing YugabyteDB Active Session History wait states in TServer and DocDB C++ code, including the macro to use for sync and async paths.
SeekDB Code Review
oceanbase/seekdb
Reviews seekdb pull requests and diffs for real defects in correctness, resources, concurrency, security and tests, reporting only Blocker or Major findings.
- Official
Add Garnet RESP Command
microsoft/garnet
Step-by-step guide for adding a new built-in RESP command to Garnet, from the command enum and parser to storage callbacks, command metadata JSON and tests.
Connection Import Wasm
feigeCode/navop
A skill your agent uses when implementing, debugging, packaging, or host-enabling onetcli WASM connection importers such as DBeaver, Navicat, Navicat Lite, Termius, connection-import.wit components…
More from maksimzayats/specx
All 12 skills in this repoSpecx Add Core Service
maksimzayats/specx
Add or refactor a specx core scope service. An agent skill from maksimzayats/specx.
Specx Add Delivery Controller
maksimzayats/specx
Add delivery controllers for specx services, especially FastAPI HTTP routes.
Specx Add Infrastructure Adapter
maksimzayats/specx
Add technical infrastructure adapters for specx core scopes.
Specx Component Architecture
maksimzayats/specx
Design or review specx core scope boundaries in Python services.
Specx Diwire Composition
maksimzayats/specx
Wire dependency injection for a specx Python service with diwire.
Specx Project Structure
maksimzayats/specx
Create or reshape a Python FastAPI service repo into the specx clean core/delivery architecture using packaged scoped foundation bases.
Related
Categories
Questions about Specx Add Core Use Case
What does Specx Add Core Use Case do?
Add or refactor a specx core scope use case. An agent skill from maksimzayats/specx. Specx Add Core Use Case is an agent skill from maksimzayats/specx. Add or refactor a specx core scope use case.
When should I use Specx Add Core Use Case?
Specx Add Core Use Case fits situations like: implementing an externally meaningful application action under a core scope usecases package; adding same-file command/query inputs; coordinating services; opening a unit-of-work transaction.
How do I install Specx Add Core Use Case in Claude Code?
Run `npx skills add maksimzayats/specx --skill specx-add-core-use-case -a claude-code`. Or copy the skill folder (skills/specx-add-core-use-case in maksimzayats/specx) into .claude/skills/specx-add-core-use-case in your project. Claude Code loads it when a task matches its description.
How do I install Specx Add Core Use Case in Codex?
Run `npx skills add maksimzayats/specx --skill specx-add-core-use-case -a codex`. Or copy the skill folder (skills/specx-add-core-use-case in maksimzayats/specx) into .agents/skills/specx-add-core-use-case in your project. Codex loads it when a task matches its description.
Can I use Specx Add Core Use Case 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 maksimzayats/specx --skill specx-add-core-use-case -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/specx-add-core-use-case, .gemini/skills/specx-add-core-use-case, .github/skills/specx-add-core-use-case and .opencode/skills/specx-add-core-use-case in your project.
What does Specx Add Core Use Case need to run?
SKILL.md names no scripts, command-line tools or credentials: Specx Add Core Use Case is instructions for the agent only.
Does Specx Add Core Use Case 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 Specx Add Core Use Case 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 Specx Add Core Use Case use?
Specx Add Core Use Case 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 Specx Add Core Use Case use?
About 1.1k tokens (SKILL.md is roughly 4.2k 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 3.5k tokens, read only when the agent opens those files.
What are the alternatives to Specx Add Core Use Case?
Skills that share tags, products or a category with Specx Add Core Use Case: Add Redis Command to go-redis (redis/go-redis, 22k stars), Citus Merge Loop (citusdata/citus, 13k stars), YugabyteDB ASH Instrumentation (yugabyte/yugabyte-db, 11k stars) and SeekDB Code Review (oceanbase/seekdb, 3.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Specx Add Core Use Case?
maksimzayats (a GitHub user) maintains it in maksimzayats/specx, which has 202 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on August 8, 2026.
Source: maksimzayats/specx on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.