Agent skill

Spec Research

by Smana in Smana/cloud-native-ref

Research patterns, ecosystem tools, and best practices before writing a design.

Apache-2.0Auto-check passedAgent Workflows

Install Spec Research

skills CLI
$ npx skills add Smana/cloud-native-ref --skill spec-research -a claude-code

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

GitHub CLI
$ gh skill install Smana/cloud-native-ref spec-research --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/Smana/cloud-native-ref.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/spec-research .claude/skills/spec-research && 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
spec-research
GitHub stars
103
Token cost
~1.1k tokens
SKILL.md length
290 words
Files
1
Skills in repo
6
Repo updated
First seen
Licence
Apache-2.0

At a glance

Research patterns, ecosystem tools, and best practices before writing a design.

  • Works in 6 steps: Frame the question → Map the local landscape first → External sources (in priority order) → …
  • Tasks that involve Context engineering
  • SKILL.md covers Your mission and Research protocol
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Spec Research is an agent skill from Smana/cloud-native-ref. Research patterns, ecosystem tools, and best practices before writing a design. Runs in a forked Explore subagent so it can query Context7, WebSearch, and the whole codebase without consuming the main context window. Writes docs/superpowers/specs/YYYY-MM-DD-<slug-research.md.

Its SKILL.md is about 1.1k 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 Agent Workflows, covering Context engineering and Subagents. The repository describes itself as: Opiniated Cloud Native Platform Reference. The licence is Apache-2.0.

When your agent uses it

  • Tasks that involve Context engineering
  • Tasks that involve Subagents

Example prompts

  • “/spec-research”

Requirements

  • Pre-approved tools (allowed-tools): Read, Grep, Glob, Bash(git:*), WebSearch, WebFetch

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Frame the question
  2. Map the local landscape first
  3. External sources (in priority order)
  4. Write research.md
  5. Constraints on this artifact
  6. Return to caller

What it can do on your machine

Read from SKILL.md and the folder at commit e5ee7e1. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Grep
    • Glob
    • Bash(git:*)
    • WebSearch
    • WebFetch

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • github.com

    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

Spec Research loads about 1.1k tokens when it runs. Until then it costs about 73 tokens; SKILL.md has 290 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~73
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k

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 Smana/cloud-native-ref at commit e5ee7e1, republished under its Apache-2.0 licence (© Smana). 290 words, ~1,098 tokens.

Download SKILL.mdSave it as .claude/skills/spec-research/SKILL.md (or your agent's skills folder).
name
spec-research
description
Research patterns, ecosystem tools, and best practices before writing a design. Runs in a forked Explore subagent so it can query Context7, WebSearch, and the whole codebase without consuming the main context window. Writes docs/superpowers/specs/YYYY-MM-DD-<slug>-research.md.
allowed-tools
Read, Grep, Glob, Bash(git:*), WebSearch, WebFetch
when_to_use
When the user says "research before designing", "what does the ecosystem say", "look at how others do this", "find existing patterns for X", "scan Context7"…
disable-model-invocation
true
argument-hint
<slug> "<research question>" — e.g. /spec-research valkey "Valkey caching composition best practices"
context
fork
agent
Explore

Spec Research Skill (subagent)

Runs in an isolated Explore-agent context. Read-only across the repo + external sources; writes exactly one file: docs/superpowers/specs/<YYYY-MM-DD>-<slug>-research.md.

Your mission

Research $ARGUMENTS to feed a Superpowers design (superpowers:brainstorming). Produce a concise, reusable research artifact the design author can build on.

Research protocol

1. Frame the question

Parse $ARGUMENTS for the topic slug (first token) and the research question (remainder). The design doc need not exist yet — write the research file so the design author can consume it.

2. Map the local landscape first

Before going external, exhaust the repo:

  • Existing compositions in the sibling Smana/crossplane-configuration repo, under apis/<api>/kcl/ — grep for analogous patterns (e.g., if researching cache, look at app/, sqlinstance/).
  • Constitution (docs/platform-constitution.md) — which rules apply to this topic?
  • ADRs (docs/decisions/) — any prior decision constrains this?
  • Prior designs (docs/superpowers/specs/) and archived specs (docs/specs/done/) — reuse patterns rather than reinvent.
  • Runtime examples: infrastructure/aws-0/, security/aws-0/, etc.
3. External sources (in priority order)
  1. Context7 via mcp__context7__resolve-library-id then mcp__context7__query-docs — up-to-date docs for any named library or operator.
  2. Official operator/vendor docs via WebFetch.
  3. Superpowers skills (the installed plugin's skills/ directory) when the research is meta — about the workflow, not the tech.
  4. WebSearch only if the above three yielded nothing — lowest signal, easiest to misquote.
4. Write research.md

Emit exactly this structure at docs/superpowers/specs/<YYYY-MM-DD>-<slug>-research.md:

markdown
# Research: <one-line question>

**Topic**: <slug>
**Conducted**: <YYYY-MM-DD>
**Researcher**: Claude (spec-research subagent)

---

## TL;DR

<3–5 bullet points: the decisions the researcher would recommend and why>

## Standard stack

<Operators, libraries, images we should use. Pin to specific versions when docs list an LTS.>

| Component | Pick | Version | Source |
|-----------|------|---------|--------|

## Local patterns worth reusing

<File paths + 1-line note on what each shows. Copy existing patterns over invention.>

- `<path>`: <why it matters>

## Don't hand-roll

<Things the ecosystem already solves. Saves the spec author from designing these.>

## Common pitfalls

<Sharp edges from ecosystem docs / community. Especially: KCL mutation (#285),
Cilium bug #43493 for prefix delegation, anything that broke in this repo before.>

## Open questions surfaced

<Items to raise as open questions during brainstorming>

- [ ] <question>
- [ ] <question>

## References

- Context7: `<library-id>` <brief excerpt>
- <Vendor doc URL>
- Local files: `<path>`, `<path>`
5. Constraints on this artifact
  • Factual, not opinionated beyond the TL;DR. Cite sources for every non-obvious claim.
  • Resist scope creep — this is not a design document; it is inputs for one.
  • No decisions, only options. Brainstorming is where decisions happen.
  • Keep under 400 lines; split into research-<topic>.md files if the topic genuinely spans multiple subdomains.
6. Return to caller

Return a 5-line summary (TL;DR bullets) back to the main context. Full detail lives in the written file.

© Smana, 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 .agents/skills/spec-research of Smana/cloud-native-ref.

Open the folder on GitHubat commit e5ee7e1

Compare with similar skills

Spec Research 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.

Spec Research compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Spec Research this skillSmana/cloud-native-ref103—~1.1kAutomated safety check: PassApache-2.0
Claude Statusbarleeguooooo/claude-code-usage-bar378—~2.5kAutomated safety check: PassMIT
Badstephenleo/bmad-autonomous-development107—~7.7kAutomated safety check: PassMIT
Analyze Trajectoryyologdev/yoyo-evolve1.9k—~3.6kAutomated safety check: PassMIT
Code Context Slicingtrailofbits/skills7.4k—~2.1kAutomated safety check: PassCC-BY-SA-4.0
MoAI Foundation Coremodu-ai/moai-adk1.2k—~5kAutomated safety check: PassApache-2.0

Similar skills

  • Claude Statusbar

    leeguooooo/claude-code-usage-bar

    Manage cs (claude-statusbar) — switch theme/style/density, override severity colors, preview combinations, run doctor, reset config, install, upgrade (cs upgrade — the only supported upgrade path)…

    378 GitHub stars~2.5k tokensUpdated today
    Agent WorkflowsAuto-check passed
  • Bad

    stephenleo/bmad-autonomous-development

    BMad Autonomous Development — orchestrates parallel story implementation pipelines.

    107 GitHub stars~7.7k tokensUpdated 5 mo ago
    Agent WorkflowsAuto-check passed
  • Analyze Trajectory

    yologdev/yoyo-evolve

    Diagnoses a recurring failure such as a stuck task, repeated CI error or frequent reverts by sending sub-agents through the logs and returning one root-cause diagnosis.

    1.9k GitHub stars~3.6k tokensUpdated today
    Agent WorkflowsAuto-check passed
  • Code Context Slicing

    trailofbits/skills

    Official

    Picks a small, graph-based slice of source with Trailmark and hands a focused code task to a smaller or local model without exposing the whole repository.

    7.4k GitHub stars~2.1k tokensUpdated yesterday
    Agent WorkflowsAuto-check passed
  • MoAI Foundation Core

    modu-ai/moai-adk

    Reference for MoAI-ADK's core development principles: TRUST 5 quality gates, SPEC-first domain-driven workflow, agent delegation and token budgeting.

    1.2k GitHub stars~5k tokensUpdated today
    Agent WorkflowsAuto-check passed
  • Cc Dev Agent

    sangrokjung/claude-forge

    A skill your agent uses when starting Claude Code projects, writing CLAUDE.md/spec.md, dispatching subagents, or requesting Agent Teams parallel development.

    852 GitHub stars~771 tokensUpdated 1 mo ago
    Agent WorkflowsAuto-check passed

More from Smana/cloud-native-ref

  • Commit

    Smana/cloud-native-ref

    Run pre-commit validation before committing. An agent skill from Smana/cloud-native-ref.

    103 GitHub stars~778 tokensUpdated today
    Auto-check passed
  • Ship It

    Smana/cloud-native-ref

    Take a finished branch through the full pre-merge pipeline in one pass — rebase onto origin/main, simplify, prune prose, run the repo's validators and cite their output, review the diff, act on…

    103 GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Sync Branch

    Smana/cloud-native-ref

    Rebase the current branch onto the latest origin/main before pushing, reviewing, or opening a PR.

    103 GitHub stars~966 tokensUpdated today
    Auto-check passed
  • Create PR

    Smana/cloud-native-ref

    Create or update a Pull Request with AI-generated description, mermaid diagram, file walkthrough, and automatic design-doc detection.

    103 GitHub stars~1.2k tokensUpdated today
    Auto-check passed
  • Verify Spec

    Smana/cloud-native-ref

    Verify that a merged design's success criteria are actually met in the live cluster.

    103 GitHub stars~1.5k tokensUpdated today
    Auto-check passed

Categories

Questions about Spec Research

What does Spec Research do?

Research patterns, ecosystem tools, and best practices before writing a design. Spec Research is an agent skill from Smana/cloud-native-ref. Research patterns, ecosystem tools, and best practices before writing a design.

When should I use Spec Research?

Spec Research fits situations like: tasks that involve Context engineering; tasks that involve Subagents.

How do I install Spec Research in Claude Code?

Run `npx skills add Smana/cloud-native-ref --skill spec-research -a claude-code`. Or copy the skill folder (.agents/skills/spec-research in Smana/cloud-native-ref) into .claude/skills/spec-research in your project. Claude Code loads it when a task matches its description.

How do I install Spec Research in Codex?

Run `npx skills add Smana/cloud-native-ref --skill spec-research -a codex`. Or copy the skill folder (.agents/skills/spec-research in Smana/cloud-native-ref) into .agents/skills/spec-research in your project. Codex loads it when a task matches its description.

Can I use Spec Research 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 Smana/cloud-native-ref --skill spec-research -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/spec-research, .gemini/skills/spec-research, .github/skills/spec-research and .opencode/skills/spec-research in your project.

What does Spec Research need to run?

SKILL.md names no scripts, command-line tools or credentials: Spec Research is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Grep, Glob, Bash(git:*), WebSearch, WebFetch.

Does Spec Research access the network?

SKILL.md names 1 domain. As links in the text: github.com. This is read from the text; nothing was executed.

Is Spec Research 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 Spec Research use?

Spec Research 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 Spec Research use?

About 1.1k tokens (SKILL.md is roughly 4.4k 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 Spec Research?

Skills that share tags, products or a category with Spec Research: Claude Statusbar (leeguooooo/claude-code-usage-bar, 378 stars), Bad (stephenleo/bmad-autonomous-development, 107 stars), Analyze Trajectory (yologdev/yoyo-evolve, 1.9k stars) and Code Context Slicing (trailofbits/skills, 7.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Spec Research?

Smana (a GitHub user) maintains it in Smana/cloud-native-ref, which has 103 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on October 9, 2026.

Source: Smana/cloud-native-ref on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.