Agent skill

Specx Add Core Service

by maksimzayats in maksimzayats/specx

Add or refactor a specx core scope service. An agent skill from maksimzayats/specx.

MITAuto-check passedDevelopment

Install Specx Add Core Service

skills CLI
$ npx skills add maksimzayats/specx --skill specx-add-core-service -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install maksimzayats/specx specx-add-core-service --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/maksimzayats/specx.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/specx-add-core-service .claude/skills/specx-add-core-service && rm -rf skills-src

Use ~/.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/

Facts

Skill name
specx-add-core-service
GitHub stars
202
Token cost
~688 tokens
SKILL.md length
304 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 service. An agent skill from maksimzayats/specx.

  • Works in 11 steps: Confirm this is reusable… → Name the behavior, not a vague role, and… → Put it under core//services/.py. → …
  • Implementing focused reusable business/application behavior under a core scope services package
  • SKILL.md covers Workflow, Code Style and References
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Specx Add Core Service is an agent skill from maksimzayats/specx. Add or refactor a specx core scope service. Use when implementing focused reusable business/application behavior under a core scope services package, extracting logic from a use case, injecting deterministic collaborators, accepting an active unit of work, choosing between Service and Capability, or keeping business decisions away from delivery and infrastructure.

Its SKILL.md is about 690 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/service.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 focused reusable business/application behavior under a core scope services package
  • Extracting logic from a use case
  • Injecting deterministic collaborators
  • Accepting an active unit of work

Example prompts

  • “/specx-add-core-service”

Workflow steps

11 steps, taken from the first numbered list in SKILL.md.

  1. Confirm this is reusable business/application behavior, not a small
  2. Name the behavior, not a vague role, and always use the Service suffix
  3. Put it under core//services/.py.
  4. Choose exactly one foundation base
  5. Do not add or use a generic BaseService.
  6. Inject concrete project collaborators when there is one implementation.
  7. Inject ports/ABCs only for external IO, framework-bound dependencies, or
  8. Add a docstring that explains the service scope and includes a concrete
  9. Keep methods keyword-only after self.
  10. Do not open UoW scopes in services. Use cases own transaction lifecycle and
  11. Add flat unit tests that receive the native pytest container fixture,

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 Service loads about 688 tokens when it runs, and up to ~2.4k if it reads all its reference files. Until then it costs about 97 tokens; SKILL.md has 304 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~97
When it runs · the whole SKILL.md, loaded when a task matches
~688
With references · SKILL.md plus every file in references/, read only if the agent opens them
~2.4k

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). 304 words, ~688 tokens.

Download SKILL.mdSave it as .claude/skills/specx-add-core-service/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-service
description
Add or refactor a specx core scope service. Use when implementing focused reusable business/application behavior under a core scope services package, extracting logic from a use case, injecting deterministic collaborators, accepting an active unit of work, choosing between Service and Capability, or keeping business decisions away from delivery and infrastructure.

specx Add Core Service

Use this skill for reusable core behavior that is smaller than an application action. Read references/service.md before writing the service.

Workflow

  1. Confirm this is reusable business/application behavior, not a small replaceable ability. Use BaseCapability instead for one narrow injectable thing.
  2. Name the behavior, not a vague role, and always use the Service suffix: InvoicePricingService, AccessPolicyService, OrderAllocationService, SubscriptionRenewalService.
  3. Put it under core/<scope>/services/<behavior>.py.
  4. Choose exactly one foundation base: BasePureService, BaseReadService, or BaseEffectService.
  5. Do not add or use a generic BaseService.
  6. Inject concrete project collaborators when there is one implementation.
  7. Inject ports/ABCs only for external IO, framework-bound dependencies, or multiple real implementations. Do not create an interface only to make a concrete collaborator mockable.
  8. Add a docstring that explains the service scope and includes a concrete Example:.
  9. Keep methods keyword-only after self.
  10. Do not open UoW scopes in services. Use cases own transaction lifecycle and pass active UoWs into read/effect services when needed.
  11. Add flat unit tests that receive the native pytest container fixture, register local doubles or inline mocks before resolution, and resolve the service with container.resolve(ServiceClass).

Operational probe services may live under core/health when readiness checks any required external dependency or policy is reused across deliveries. Keep simple process liveness in delivery. Use a pure service for reusable liveness policy and a read service for readiness coordination. Readiness services depend on gateway ports, not SQLAlchemy, Redis, SDKs, or delivery frameworks directly. Technical readiness adapters must bound external checks with short timeouts so a probe cannot hang indefinitely.

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/service.md - class shape, dependency choices, UoW parameter rules, and unit-test examples.

© 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-service of maksimzayats/specx.

  • SKILL.md
  • agents/openai.yaml
  • references/service.md

Open the folder on GitHubat commit 9362406

Compare with similar skills

Specx Add Core Service 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.

Specx Add Core Service compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Specx Add Core Service this skillmaksimzayats/specx202—~688Automated safety check: PassMIT
Vercel Composition Patternssupabase/supabase111k58 repos~726Automated safety check: PassMIT
Finishing a Development Branchobra/superpowers297k5 repos~1.9kAutomated safety check: PassMIT
Typescript Advanced Typesrolling-scopes/rsschool-app10k25 repos~4.2kAutomated safety check: PassMPL-2.0
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Code Review ChecklistshareAI-lab/learn-claude-code78k4 repos~1.1kAutomated safety check: PassMIT

Similar skills

  • Official

    React composition patterns that scale. An agent skill from supabase/supabase.

    111k GitHub starsUsed in 58 repos~726 tokens
    DevelopmentAuto-check passed
  • Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.

    297k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed
  • Typescript Advanced Types

    rolling-scopes/rsschool-app

    Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications.

    10k GitHub starsUsed in 25 repos~4.2k tokens
    DevelopmentAuto-check passed
  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed
  • Code Review Checklist

    shareAI-lab/learn-claude-code

    Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.

    78k GitHub starsUsed in 4 repos~1.1k tokens
    DevelopmentAuto-check passed
  • Greploop

    onyx-dot-app/onyx

    Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until Greptile gives it a 5/5 confidence score with zero unresolved comments.

    32k GitHub starsUsed in 4 repos~3.3k tokens
    DevelopmentAuto-check passed

More from maksimzayats/specx

All 12 skills in this repo
  • Specx Add Core Use Case

    maksimzayats/specx

    Add or refactor a specx core scope use case. An agent skill from maksimzayats/specx.

    202 GitHub stars~1.1k tokensUpdated 2 mo ago
    Auto-check passed
  • Add delivery controllers for specx services, especially FastAPI HTTP routes.

    202 GitHub stars~704 tokensUpdated 2 mo ago
    Auto-check passed
  • Add technical infrastructure adapters for specx core scopes.

    202 GitHub stars~1k tokensUpdated 2 mo ago
    Auto-check passed
  • Design or review specx core scope boundaries in Python services.

    202 GitHub stars~1.8k tokensUpdated 2 mo ago
    Auto-check passed
  • Specx Diwire Composition

    maksimzayats/specx

    Wire dependency injection for a specx Python service with diwire.

    202 GitHub stars~1.1k tokensUpdated 2 mo ago
    Auto-check passed
  • 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.

    202 GitHub stars~1.5k tokensUpdated 2 mo ago
    Auto-check passed

Categories

Questions about Specx Add Core Service

What does Specx Add Core Service do?

Add or refactor a specx core scope service. An agent skill from maksimzayats/specx. Specx Add Core Service is an agent skill from maksimzayats/specx. Add or refactor a specx core scope service.

When should I use Specx Add Core Service?

Specx Add Core Service fits situations like: implementing focused reusable business/application behavior under a core scope services package; extracting logic from a use case; injecting deterministic collaborators; accepting an active unit of work.

How do I install Specx Add Core Service in Claude Code?

Run `npx skills add maksimzayats/specx --skill specx-add-core-service -a claude-code`. Or copy the skill folder (skills/specx-add-core-service in maksimzayats/specx) into .claude/skills/specx-add-core-service in your project. Claude Code loads it when a task matches its description.

How do I install Specx Add Core Service in Codex?

Run `npx skills add maksimzayats/specx --skill specx-add-core-service -a codex`. Or copy the skill folder (skills/specx-add-core-service in maksimzayats/specx) into .agents/skills/specx-add-core-service in your project. Codex loads it when a task matches its description.

Can I use Specx Add Core Service 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-service -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-service, .gemini/skills/specx-add-core-service, .github/skills/specx-add-core-service and .opencode/skills/specx-add-core-service in your project.

What does Specx Add Core Service need to run?

SKILL.md names no scripts, command-line tools or credentials: Specx Add Core Service is instructions for the agent only.

Does Specx Add Core Service 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 Service 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 Service use?

Specx Add Core Service 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 Service use?

About 688 tokens (SKILL.md is roughly 2.8k 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 1.7k tokens, read only when the agent opens those files.

What are the alternatives to Specx Add Core Service?

Skills that share tags, products or a category with Specx Add Core Service: Vercel Composition Patterns (supabase/supabase, 111k stars), Finishing a Development Branch (obra/superpowers, 297k stars), Typescript Advanced Types (rolling-scopes/rsschool-app, 10k stars) and PR Babysitter (openinterpreter/openinterpreter, 69k 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 Service?

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.