How do I install the Sk Claude Code Conventions skill?

Run npx skillmds@latest add gustavo-meilus/sk-claude-code-conventions in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Sk Claude Code Conventions safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Sk Claude Code Conventions?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Sk Claude Code Conventions free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Sk Claude Code Conventions?

gustavo-meilus (@gustavo-meilus) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Sk Claude Code Conventions by gustavo-meilus

Name: Sk Claude Code Conventions
Author: gustavo-meilus

Sk Claude Code Conventions

Provides canonical engineering standards for authoring agents, skills, hooks, and pipeline orchestration in Claude Code. Use when authoring or modifying agents, skills, hooks, or pipeline-orchestration artifacts — covers model-tier selection, prompt-cache discipline, frontmatter schemas, and progressive-disclosure rules.

File contents

Claude Code Conventions — Reference

Model & Reasoning Selection

Caching & Context Discipline

2. CACHE BREAKPOINTS

Up to 4 cache_control breakpoints are supported.
The final breakpoint belongs on the last block that remains identical across requests.
Agentic loops use 1-hour TTL to prevent cache expiration between turns.

Artifact Schemas

Skill Frontmatter

name: {lowercase-hyphens}
description: {triggering-only, third person}
effort: {low | medium | high | xhigh | max}
disable-model-invocation: {boolean}
user-invocable: {boolean}

Agent Frontmatter

name: {identifier}
description: {action-oriented trigger}
effort: {high for architects, medium for workers}
isolation: worktree
skills: [sk-4d-method, sk-spec-driven-development]

Progressive Disclosure Checklist

Reference Files

sk-pipeline-state/SKILL.md — State management rules.
sk-pipeline-paths/SKILL.md — Scope-aware path resolution.
sk-4d-method/SKILL.md — Per-invocation wrapper.
sk-spec-driven-development/SKILL.md — SDD protocol.

---name: sk-claude-code-conventionsdescription: Provides canonical engineering standards for authoring agents, skills, hooks, and pipeline orchestration in Claude Code. Use when authoring or modifying agents, skills, hooks, or pipeline-orchestration artifacts — covers model-tier selection, prompt-cache discipline, frontmatter schemas, and progressive-disclosure rules.---# Claude Code Conventions — Reference<glossary> <term name="Adaptive Thinking">Model-driven reasoning scaled by the `effort` parameter.</term> <term name="Prompt Caching">A mechanism to persist static context (system prompts, skills) to reduce latency and cost.</term> <term name="Progressive Disclosure">Structuring content into layers (Body → References) to minimize context bloat.</term></glossary>## Model & Reasoning Selection<model_tier_table>| Tier | Model ID | Application || :--- | :--- | :--- || `triage` | `claude-haiku-4-5-20251001` | High-volume, low-latency classification. || `fast` | `claude-haiku-4-5-20251001` | Reviews and bounded worker steps. || `medium` | `claude-sonnet-4-6` | Default for pipelines, agents, and skills. || `deep` | `claude-opus-4-8` | High-complexity architecture or auditing tasks. |</model_tier_table><invariant>This skill is Claude Code-scoped (Tier 1 only). Concrete model IDs above describe the Tier 1 resolution of the `MODEL_SELECTION: TIER_BASED_RUNTIME_RESOLVED` invariant — i.e., Tier 1's `platform_profile.model_tiers.medium` resolves to `claude-sonnet-4-6`, `.fast`/`.triage` to `claude-haiku-4-5-20251001`, and `.deep` to `claude-opus-4-8`. On other tiers the same `fast`/`deep` slots resolve to that platform's idiomatic models (see `skills/sk-platform-dispatch/profiles/{tier_id}.json`). Per `DEPENDENCY_INVERSION: PROFILE_DRIVEN`, pipeline-architect and other tier-agnostic skills MUST consult `platform_profile.model_tiers` rather than the CC literals shown here. Reasoning scales within-tier via `effort`; tier switches are warranted only when the step category genuinely differs.</invariant>## Caching & Context Discipline<protocol>### 1. CACHE STABILITY- **Static First**: Context ordered as System Prompt → Skills → Tools → Conversation History.- **Invariant Toolsets**: Tool and skill lists must not be mutated mid-session; mutation invalidates the entire prefix.- **Static Headers**: Dynamic timestamps or mutable data must not appear in the static system prefix.### 2. CACHE BREAKPOINTS- Up to 4 `cache_control` breakpoints are supported.- The final breakpoint belongs on the last block that remains identical across requests.- Agentic loops use 1-hour TTL to prevent cache expiration between turns.</protocol>## Artifact Schemas### Skill Frontmatter<invariant>`SKILL.md` bodies must not exceed 500 lines. Descriptions must use third-person voice and focus strictly on triggering conditions.</invariant>```yamlname: {lowercase-hyphens}description: {triggering-only, third person}effort: {low | medium | high | xhigh | max}disable-model-invocation: {boolean}user-invocable: {boolean}```### Agent Frontmatter<invariant>Agent bodies must not exceed 150 lines. Depth belongs in companion `<agent>-references/references/*.md` files.</invariant>```yamlname: {identifier}description: {action-oriented trigger}effort: {high for architects, medium for workers}isolation: worktreeskills: [sk-4d-method, sk-spec-driven-development]```<invariant>Plugin-scope enforcement rule: Claude Code ignores `permissionMode`, `hooks`, and `mcpServers` on subagents loaded from a plugin — only `tools:` and `disallowedTools:` are enforced on that path. Reviewer write-deny for plugin-shipped agents therefore rests entirely on the tool allowlist; `permissionMode` in `agents/*.md` is declarative intent, not a barrier. Project-scope agents (including agents MATERIALIZE writes under `.claude/agents/superpipelines/{P}/`) enforce `permissionMode` normally. No document may claim `permissionMode` enforcement for plugin-shipped agents (auditor BUNDLE-08).</invariant>## Progressive Disclosure Checklist<checklist>- [ ] `SKILL.md` body ≤500 lines.- [ ] References are exactly one level deep from `SKILL.md`.- [ ] References >100 lines include a Table of Contents.- [ ] Descriptions are third-person and triggering-only.- [ ] Examples are concrete and specific to the domain.</checklist><invariants>- `memory: project` must not appear in agent frontmatter.- All relative paths must be resolved via `${CLAUDE_PLUGIN_ROOT}` or `${CLAUDE_PLUGIN_DATA}`.- All pipeline state must be persisted to the canonical `pipeline-state.json` location.</invariants>## Reference Files- `sk-pipeline-state/SKILL.md` — State management rules.- `sk-pipeline-paths/SKILL.md` — Scope-aware path resolution.- `sk-4d-method/SKILL.md` — Per-invocation wrapper.- `sk-spec-driven-development/SKILL.md` — SDD protocol.

Frequently asked questions