cloud-native-ref: Skill for Claude Code

.agents/skills/spec-research/SKILL.md

spec-research is a skill for Claude Code from Smana/cloud-native-ref. It costs 65 tokens per session (1,080 once invoked), scanned A, original, Apache-2.0.

A research workflow that investigates a technical topic before a software design is written. It examines the repository and related sources, then saves one dated research document.

In plain words
What is it for?
Researching implementation patterns, checking project rules and past decisions, finding similar code, and producing a research note for a later design.
Why use it?
Design work often misses existing code, project rules, or earlier decisions. This gathers that context first so the design can build on what is already known.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: agent in frontmatter; mentions subagents; installed under .agents/ (shared by several agents).

This is Smana/cloud-native-ref's own configuration. It tells Claude Code how to work on cloud-native-ref itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything cloud-native-ref configures →

Reuse

Borrowing it

Nothing to install: this file belongs to Smana/cloud-native-ref. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/Smana/cloud-native-ref/main/.agents/skills/spec-research/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/Smana/cloud-native-ref

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for spec-research

README.md
[![agentmods](https://agentmods.dev/badge/skills/smana/cloud-native-ref/spec-research/github.svg)](https://agentmods.dev/skills/smana/cloud-native-ref/spec-research)
Your own site
<a href="https://agentmods.dev/skills/smana/cloud-native-ref/spec-research"><img src="https://agentmods.dev/badge/skills/smana/cloud-native-ref/spec-research/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for spec-research

Your own site · 80×15
<a href="https://agentmods.dev/skills/smana/cloud-native-ref/spec-research"><img src="https://agentmods.dev/badge/skills/smana/cloud-native-ref/spec-research.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 65 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,080 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00065 $0.01080
Opus 5.5 $0.00026 $0.00432
Sonnet 5.5 $0.00013 $0.00216
Haiku 4.5 $0.00006 $0.00108

Measured 1mo ago against content hash 0e134566aafc, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

spec-research scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.agents/skills/spec-research/SKILL.md · 110 lines

How it starts

The opening of the file, as written. The whole thing — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.

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:

# 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>`

Read the full file on GitHub · 110 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 1mo ago First seen · 110 lines · 65 tokens per session scan A 0e134566aafc

Subscribe to this mod's changes

spec-research is a skill published in the GitHub repository Smana/cloud-native-ref (104 stars, last pushed today), licensed Apache-2.0. It adds 65 tokens to every session and 1,080 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

cloud-sync

Set up or check claude-mem cloud sync with cmem.ai Pro. Use when the user says "set up cloud sync", "sync my memories", "cmem pro", "cloud backup", "sync status", or wants their memory database backed up or synced to their cmem.ai account.

thedotmack/claude-mem · 64 tokens

troubleshoot-sandbox

Troubleshoot OpenSandbox issues by running diagnostics (logs, inspect, events, summary) via CLI or HTTP API to diagnose sandbox failures like OOM, crash, image pull errors, network problems, etc.

opensandbox-group/OpenSandbox · 48 tokens

network-rca

Kubernetes network root cause analysis skill powered by Kubeshark MCP. Use this skill whenever the user wants to investigate past incidents, perform retrospective traffic analysis, take or manage traffic snapshots, extract PCAPs, dissect L7 API calls from historical captures, compare traffic patterns over time, detect…

kubeshark/kubeshark · 163 tokens

mirrord-prev-env

Help users create and manage mirrord preview environments — running a modified service as an isolated pod in a shared Kubernetes cluster, scoped by an environment key and HTTP/queue traffic filtering, so teams can validate and review changes against real traffic without affecting live services. Use when a developer…

metalbear-co/mirrord · 122 tokens

mirrord-kafka

Helps DevOps engineers configure mirrord Operator's Kafka queue splitting feature end-to-end. Generates the MirrordSplitConfig and MirrordPropertyList Kubernetes CRD YAMLs (the current resources; MirrordKafkaTopicsConsumer + MirrordKafkaClientConfig are deprecated but still supported), the matching mirrord.json…

metalbear-co/mirrord · 189 tokens

mirrord-operator

Help users install and configure the mirrord Operator for team/enterprise environments. Use when users ask about operator setup, Helm installation, cloud API key or license configuration, air-gapped/offline licensing, enabling features (queue splitting, DB branching, preview environments, multi-cluster), internal…

metalbear-co/mirrord · 124 tokens