Ss Resolve Agent Skill

Compile a small, deterministic StyleSeed rule bundle for one agent, output grammar, surface adapter, domain, page type, brand recipe, and optional profile. Use before setup or build, when STYLESEED.md changes, when updating StyleSeed, or whenever an agent would otherwise load the full rule handbook.

17k tokens

context cost

the whole folder, loaded on every use

files

ships runnable scripts

copies elsewhere

how many repositories repackaged it

866

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/bitjaru/styleseed --skill ss-resolve

The instruction itself

1 sections, as written by the author

Resolve effective StyleSeed context

Use the bundled scripts/resolve-context.mjs; do not hand-compose the rule stack.

Read STYLESEED.md when it exists. Confirm missing required selections with the user.
Keep the working directory at the user's project root. Invoke the script by its installed

path; do not cd into the skill directory. Prefer --from-lock STYLESEED.md; explicit flags

override lock values.

Read the emitted .styleseed/effective-rules.md before building.
Preserve .styleseed/manifest.json. It records selections, source hashes, and the bundle hash

for updates and reproducibility.

Use --check to detect context drift without rewriting files.

node <installed-ss-resolve>/scripts/resolve-context.mjs \
  --from-lock STYLESEED.md \
  --agent codex

Without a lock:

node <installed-ss-resolve>/scripts/resolve-context.mjs \
  --agent claude \
  --grammar operations-console \
  --adapter product-ui \
  --domain saas \
  --page dashboard \
  --recipe enterprise-workbench \
  --profile swiss

Use --list to print supported IDs. --recipe auto maps the selected grammar to a maintained

default; pass an explicit recipe when the product needs a different morphology. The default

output directory is .styleseed/ in the

project root. For a project-local reference grammar, pass reference:<slug> and ensure

.styleseed/rulesets/<slug>/RULESET.md exists.

Do not load llms-full.txt after a bundle resolves successfully. Load a larger source document

only when the bundle names an unresolved ambiguity that requires it.

Other skills for the same job

different authors, same section of the catalogue

Skill Creator

by anthropics

vendor ×10

Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.

Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.

Replace with description of the skill and when Claude should use it.

35 tokens

Dispatching Parallel Agents

by ZhanlinCui

×5

Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies

This skill should be used when the user wants to "create a skill", "add a skill to plugin", "write a new skill", "improve skill description", "organize skill content", or needs guidance on skill structure, progressive disclosure, or skill development best practices for Claude Code plugins.

Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.

Use when creating new skills, editing existing skills, or verifying skills work before deployment

26k tokens scripts

How to use it

Copy the folder

Take bitjaru/ss-resolve from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.