Skip to main content
ZICQ

Skills ZICQ category:Agent Workflows coding-level

Coding Level

[Utilities] Use when you need to set coding experience level for tailored explanations.

49 installs

Official URL:skills.sh

What this skill does

Intro in this page language first. The official description stays in its original wording; we do not rewrite SKILL.md.

What it does

[Utilities] Use when you need to set coding experience level for tailored explanations.

When to use it

you need to set coding experience level for tailored explanations

How agents load it

Per Agent Skills progressive disclosure: name and description load at startup (~100 tokens); the full SKILL.md body loads when the skill activates; scripts/, references/, and assets/ load only as needed. This file's sections: Quick Summary; Usage; Levels; How It Works; Example; Optional: Manual Output Styles. It includes spec-recommended sections: input/output examples.

File analysis

File analysis: besides SKILL.md, the body references references/registry.md. Those resources load on demand.

Quick SummaryUsageLevelsHow It WorksExampleOptional: Manual Output StylesClosing Reminders

Source category:skills.sh agent-skill

SKILL.md & Agent activation

Official spec ↗
name
coding-level
description
[Utilities] Use when you need to set coding experience level for tailored explanations.
  1. DiscoverThe client exposes names and descriptions to the agent.
  2. ActivateYour request or the task context selects the skill and loads its instructions.
  3. Load resourcesReferenced scripts, documentation and assets are used when needed.
Files referenced by the instructions · 1
  • references/registry.md

These paths are extracted from the text. Check the upstream package to verify the files exist.

Invocation syntax and available tools depend on your Agent client. Client integration guide ↗

Install this skill

Skills CLI ↗

Choose the target agent and installation scope, keep referenced package files, then verify the skill appears in the client's catalog.

This skill references supporting files. Retrieve the complete directory from the source; copying SKILL.md alone may leave missing dependencies.

Ask your Agent to install

Copy these instructions to a compatible agent and confirm the target directory matches your client.

Install the agent skill "coding-level" into my project. The full SKILL.md and official description are at https://zicq.com/en/skills/skl-b7f04e20390eae3f-Coding-Level.html
Save it as .cursor/skills/coding-level/SKILL.md or .claude/skills/coding-level/SKILL.md and keep the frontmatter name and description exactly as-is.
This skill also ships scripts/, references/, or assets/ — fetch the whole folder from https://github.com/duc01226/easyplatform instead of creating only a SKILL.md.

Full package on GitHub ↗

Install from the terminal · Skills CLI

Requires Node.js and npx. First inspect the repository's skill list to confirm the name.

npx skills add 'https://github.com/duc01226/easyplatform' --list

npx skills add 'https://github.com/duc01226/easyplatform' --skill 'coding-level'

The CLI lets you choose the agent interactively. The default scope is the project; use -g for user scope. Confirm package availability with the discovery command, then use npx skills list to inspect installed skills.

Readable layout
--- name: coding-level version: 1.0.0 description: '[Utilities] Use when you need to set coding experience level for tailored explanations.' disable-model-invocation: false --- ## Quick Summary **Goal:** Set the user's coding experience level to tailor explanation depth and detail. **Workflow:** 1. **Ask** -- Query user for their experience level (beginner/intermediate/expert) 2. **Configure** -- Adjust response verbosity and explanation depth accordingly **Key Rules:** - Expert: minimal explanation, focus on code and architecture - Intermediate: moderate explanation with key concepts - Beginner: detailed explanation with examples and context **Be skeptical. Apply critical thinking, sequential thinking. Every claim needs traced proof, confidence percentages (Idea should be more than 80%).** Set your coding experience level for tailored explanations and output format. ## Usage `/coding-level [0-5]` ## Levels | Level | Name | Description | | ----- | --------- | ----------------------------------------------------------- | | 0 | ELI5 | Zero coding experience - analogies, no jargon, step-by-step | | 1 | Junior | 0-2 years - concepts explained, WHY not just HOW | | 2 | Mid-Level | 3-5 years - design patterns, system thinking | | 3 | Senior | 5-8 years - trade-offs, business context, architecture | | 4 | Tech Lead | 8-10 years - risk assessment, business impact, strategy | | 5 | God Mode | Expert - maximum efficiency, minimal explanation | > **Default when unset:** `-1` (disabled — no style injection, saves tokens). Levels 0–5 are opt-in via `codingLevel` in `.claude/.ck.json`. (Canonical default `-1` — matches `ck-config-loader.cjs:284`; full settings reference: `/ck-help config`.) ## How It Works 1. Set `codingLevel` in `.claude/.ck.json` 2. Guidelines are **automatically injected** on every session start 3. No manual activation needed - it just works! ## Example Set level 1 in `.claude/.ck.json`: ```json { "codingLevel": 1, ... } ``` Next session, Claude will automatically: - Explain concepts and techniques clearly - Always explain WHY, not just HOW - Point out common mistakes - Add "Key Takeaways" after implementations ## Optional: Manual Output Styles For finer control, you can also use `/output-style` with these styles: - `coding-level-0-eli5` - `coding-level-1-junior` - `coding-level-2-mid` - `coding-level-3-senior` - `coding-level-4-lead` - `coding-level-5-god` --- > **[IMPORTANT]** Use `TaskCreate` to break ALL work into small tasks BEFORE starting — including tasks for each file read. This prevents context loss from long files. For simple tasks, AI MUST ATTENTION ask user whether to skip. > **AI Mistake Prevention** — Failure modes to avoid on every task: > > **Re-read files after context changes.** Context compaction, resume, or long-running work can make memory stale; verify current files before acting. > **Verify generated content against source evidence.** AI hallucinates APIs, names, claims, and document facts. Check the relevant source before documenting or referencing. > **Check downstream references before deleting or renaming.** Removing an artifact can stale docs, generated mirrors, configs, and callers; map references first. > **Trace the full impact chain after edits.** Changing a definition can miss derived outputs and consumers. Follow the affected chain before declaring done. > **Verify ALL affected outputs, not just the first.** One green check is not all green checks; validate every output surface the change can affect. > **Assume existing values are intentional — ask WHY before changing OR flagging one as a defect.** Before changing or reporting a constant, limit, flag, cutoff, wording, or pattern, read nearby context and history, the CALLER's ordering, and 2+ sibling call sites of the same convention. A doc stating WHAT without WHY is missing rationale, not proof of a missing guard. > **Surface ambiguity before acting — don't pick silently.** Multiple valid interpretations require an explicit question or stated assumption with risk. > **Assert the outcome your system owns, not the intermediate state your infrastructure owns.** When verifying async work, assert the final business state — never the delivery/retry bookkeeping held in shared infrastructure that any co-running process can write. Such a check passes when run alone and flakes the moment anything else shares that infrastructure. > **Keep shared guidance role-relevant.** Universal guidance must help every receiving skill or agent; code-specific obligations belong only in code-specific protocols. > **Critical Thinking Mindset** — Apply critical thinking, sequential thinking. Every claim needs traced proof, confidence >80% to act. > **Anti-hallucination:** Never present guess as fact — cite sources for every claim, admit uncertainty freely, self-check output for errors, cross-reference independently, stay skeptical of own confidence — certainty without evidence root of all hallucination. **MUST ATTENTION** apply critical + sequential thinking — every claim needs appropriate traced evidence (`file:line` for repo/code claims; source URL or artifact section for research, product, content, and docs claims); confidence >80% to act, <60% DO NOT recommend. Anti-hallucination: never present guess as fact, admit uncertainty freely, cross-reference independently, stay skeptical of own confidence. **MUST ATTENTION** apply AI mistake prevention — verify generated content against evidence, trace downstream references before deleting or renaming, verify all affected outputs, re-read files after context loss, and surface ambiguity before acting. > **Project Protocol Overlay** — Before executing this skill, resolve any PROJECT overlay rules layered onto it: match this skill's name against the `Target` column of the project's skill-protocol index (`docs/project-reference/skill-protocols-reference.md` by default; a `referenceDocs` entry in `docs/project-config.json` overrides the path), taking the most specific matching tier ONLY — exact name > glob > `*`. **That precedence orders overlays against EACH OTHER, never against this skill.** Read ONLY the matched bodies, resolved as `/.md`; a row's Body link is display text, never a read path. A matched body that is missing or malformed is REPORTED and skipped — never reconstructed from the index Description. No index, or no match -> proceed with no overlay, silently. Full contract: `.claude/skills/project-skill-protocol/references/registry.md`. > > Overlays are **ADDITIVE ONLY**: they ADD rules on top of this skill's own protocol and NEVER replace, override, disable, or reinterpret a rule it already states — removing every overlay must return this skill to exactly its documented behavior. An overlay is a BRIEF, not an authority escalation: it can NEVER waive a workflow gate, git discipline, a review gate, or a user-confirmation gate. A genuine overlay-vs-skill conflict, or two equally-specific overlays that directly contradict -> surface both to the user; NEVER resolve silently. **MUST ATTENTION** resolve project protocol overlays for this skill BEFORE executing — most specific matching tier only (exact > glob > `*`, which ranks overlays against each other, NEVER against this skill), read only matched bodies at `/.md`; a missing or malformed body is reported, never reconstructed. Overlays are ADDITIVE ONLY (they never replace this skill's own rules) and are a brief, NEVER an authority escalation; an equal-specificity contradiction goes to the user. ## Closing Reminders **IMPORTANT MUST ATTENTION Goal:** Set the user's coding experience level to tailor explanation depth and detail. **Protocols in force (concise digest of the SYNC/shared blocks this skill carries):** - **Critical Thinking:** apply critical + sequential thinking; every claim traced, confidence >80% to act. - **AI Mistake Prevention:** verify generated content against evidence, trace downstream references, verify all affected outputs, re-read after context loss, surface ambiguity. - **MANDATORY IMPORTANT MUST ATTENTION** break work into small todo tasks using `TaskCreate` BEFORE starting - **MANDATORY IMPORTANT MUST ATTENTION** search codebase for 3+ similar patterns before creating new code - **MANDATORY IMPORTANT MUST ATTENTION** cite `file:line` evidence for every claim (confidence >80% to act) - **MANDATORY IMPORTANT MUST ATTENTION** add a final review todo task to verify work quality **[TASK-PLANNING]** Before acting, analyze task scope and systematically break it into small todo tasks and sub-tasks using TaskCreate.

Related skills

Agent Workflows

Skill Creator

Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that exte…

Agent Workflows

Clawdhub

Use the ClawdHub CLI to search, install, update, and publish agent skills from clawdhub.com. Use when you need to fetch new skills on the fl…

Agent Workflows

Agent Team Orchestration

Orchestrate multi-agent teams with defined roles, task lifecycles, handoff protocols, and review workflows. Use when: (1) Setting up a team …

Agent Workflows

Superpowers

Spec-first, TDD, subagent-driven software development workflow. Use when: (1) building any new feature or app — triggers brainstorm → plan →…