MCP Server Builder
anthropics/skills
Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.
Judge how a memory changes active-task state and whether it refers to an existing task.
$ npx skills add sno-ai/sno-station --skill judge-task-lifecycle -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install sno-ai/sno-station judge-task-lifecycle --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/sno-ai/sno-station.git skills-src && mkdir -p .claude/skills && cp -r skills-src/packages/memory/skills/judge-task-lifecycle .claude/skills/judge-task-lifecycle && rm -rf skills-srcUse ~/.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/
Install the "judge-task-lifecycle" agent skill from https://github.com/sno-ai/sno-station/tree/main/packages/memory/skills/judge-task-lifecycle into .claude/skills/judge-task-lifecycle/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "judge-task-lifecycle", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/sno-ai/sno-station/tree/main/packages/memory/skills/judge-task-lifecycleType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add sno-ai/sno-station --skill judge-task-lifecycle -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install sno-ai/sno-station judge-task-lifecycle --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sno-ai/sno-station.git skills-src && mkdir -p .agents/skills && cp -r skills-src/packages/memory/skills/judge-task-lifecycle .agents/skills/judge-task-lifecycle && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "judge-task-lifecycle" agent skill from https://github.com/sno-ai/sno-station/tree/main/packages/memory/skills/judge-task-lifecycle into .agents/skills/judge-task-lifecycle/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "judge-task-lifecycle", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add sno-ai/sno-station --skill judge-task-lifecycle -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install sno-ai/sno-station judge-task-lifecycle --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sno-ai/sno-station.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/packages/memory/skills/judge-task-lifecycle .cursor/skills/judge-task-lifecycle && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "judge-task-lifecycle" agent skill from https://github.com/sno-ai/sno-station/tree/main/packages/memory/skills/judge-task-lifecycle into .cursor/skills/judge-task-lifecycle/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "judge-task-lifecycle", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/sno-ai/sno-station.git --path packages/memory/skills/judge-task-lifecycle--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add sno-ai/sno-station --skill judge-task-lifecycle -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install sno-ai/sno-station judge-task-lifecycle --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sno-ai/sno-station.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/packages/memory/skills/judge-task-lifecycle .gemini/skills/judge-task-lifecycle && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "judge-task-lifecycle" agent skill from https://github.com/sno-ai/sno-station/tree/main/packages/memory/skills/judge-task-lifecycle into .gemini/skills/judge-task-lifecycle/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "judge-task-lifecycle", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install sno-ai/sno-station judge-task-lifecycleInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add sno-ai/sno-station --skill judge-task-lifecycle -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/sno-ai/sno-station.git skills-src && mkdir -p .github/skills && cp -r skills-src/packages/memory/skills/judge-task-lifecycle .github/skills/judge-task-lifecycle && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "judge-task-lifecycle" agent skill from https://github.com/sno-ai/sno-station/tree/main/packages/memory/skills/judge-task-lifecycle into .github/skills/judge-task-lifecycle/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "judge-task-lifecycle", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add sno-ai/sno-station --skill judge-task-lifecycle -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install sno-ai/sno-station judge-task-lifecycle --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sno-ai/sno-station.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/packages/memory/skills/judge-task-lifecycle .opencode/skills/judge-task-lifecycle && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "judge-task-lifecycle" agent skill from https://github.com/sno-ai/sno-station/tree/main/packages/memory/skills/judge-task-lifecycle into .opencode/skills/judge-task-lifecycle/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "judge-task-lifecycle", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
judge-task-lifecycleJudge how a memory changes active-task state and whether it refers to an existing task.
Judge Task Lifecycle is an agent skill from sno-ai/sno-station. Judge how a memory changes active-task state and whether it refers to an existing task. Use for mem-claw task-lifecycle model calls.
Its SKILL.md is about 680 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. The repository describes itself as: Sno Station — your Claude Code and Codex working as one squad on your own machine. Shared encrypted memory, agent-to-agent messaging (Reach), squad skills for handoff and… The licence is Apache-2.0.
3 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit ad95c1c. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Judge Task Lifecycle loads about 679 tokens when it runs. Until then it costs about 38 tokens; SKILL.md has 414 words of instructions outside code blocks.
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.
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.
The full file from sno-ai/sno-station at commit ad95c1c, republished under its Apache-2.0 licence (© sno-ai). 414 words, ~679 tokens.
.claude/skills/judge-task-lifecycle/SKILL.md (or your agent's skills folder).Judge task meaning. Do not decide from exact wording alone.
Apply the To-do Boundary section supplied from extract-atomic-memory before these state rules.
Decide in this order and stop at the first step that applies.
complete or remove on THAT task.
Never open_or_refine, and never none.
A report ("I finished X", "X is done") and an instruction ("mark X complete", "tick X off",
"close X", "remove X from my list") both land here. An instruction to change a task's state
IS the state change; do not treat it as a request you decline to act on.
A candidate that speaks about an active task's ending is never a new task, however it is worded,
and restating the task's name inside such a sentence is naming the task to close, not opening one.open_or_refine.none.open_or_refine only for a current task that remains active.complete only when the candidate says an active task was achieved.remove only when the candidate says an active task was cancelled or should no longer be tracked.complete, even when it is
phrased as an edit to a list — "mark X complete on my todo list" and "tick X off" are complete,
not remove. Taking a finished task off a list is what completing it looks like; the words that
decide are whether the work was done. Reserve remove for a task abandoned, cancelled, called off,
no longer needed, or added by mistake — cases where the work will NOT happen.none when the candidate does not change active-task state.same_instance when the assertion refers to one listed active task, including different wording with the same meaning.distinct_instance when the assertion is a different active task.none when the assertion does not describe an active-task relation.uncertain when the evidence does not settle the relation.© sno-ai, 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
Just SKILL.md in packages/memory/skills/judge-task-lifecycle of sno-ai/sno-station.
Open the folder on GitHubat commit ad95c1c
Judge Task Lifecycle 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Judge Task Lifecycle this skillsno-ai/sno-station | 542 | — | ~679 | Automated safety check: Pass | Apache-2.0 | |
| MCP Server Builderanthropics/skills | 180k | 63 repos | ~2.3k | Automated safety check: Pass | Apache-2.0 | |
| Hook Development for Claude Code Pluginsanthropics/claude-plugins-official | 38k | 10 repos | ~4.1k | Automated safety check: Notes | Apache-2.0 | |
| Using Superpowersfarm-fe/farm | 5.6k | 36 repos | ~1.4k | Automated safety check: Pass | MIT | |
| Executing Plans Inlineobra/superpowers | 297k | 2 repos | ~5.1k | Automated safety check: Pass | MIT | |
| Skill CreatorAzure/azqr | 796 | 89 repos | ~8.2k | Automated safety check: Pass | Apache-2.0 |
anthropics/skills
Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.
anthropics/claude-plugins-official
Explains how to write Claude Code plugin hooks, both prompt-based checks and bash commands, for events such as PreToolUse, Stop and SessionStart.
farm-fe/farm
A skill your agent uses when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
obra/superpowers
Has the agent carry out an implementation plan itself, task by task in the current session, keeping a ledger, proving each step with a test and ending with one whole-branch review.
Azure/azqr
Create new skills, modify and improve existing skills, and measure skill performance.
anthropics/claude-plugins-official
Explains how to write agents for Claude Code plugins: the markdown file with YAML frontmatter, trigger descriptions, model and color settings, and system prompt design.
sno-ai/sno-station
Read one conversation window and return every independently mutable claim it states, one record each, with who or what it is about, whether it happened or stands, and the words that carry its time.
sno-ai/sno-station
Judge REM memory relations, rewrites, verification, and clause carry by meaning.
sno-ai/sno-station
Judge whether one stored row states a retired profile position as current.
sno-ai/sno-station
Understand temporal meaning in context without performing calendar arithmetic.
sno-ai/sno-station
Judge which offered rows one nominated statement retires or replaces.
sno-ai/sno-station
Resolve a new entity display name to an existing entity id or to a new entity.
Categories
Judge how a memory changes active-task state and whether it refers to an existing task. Judge Task Lifecycle is an agent skill from sno-ai/sno-station. Judge how a memory changes active-task state and whether it refers to an existing task.
Judge Task Lifecycle fits situations like: mem-claw task-lifecycle model calls.
Run `npx skills add sno-ai/sno-station --skill judge-task-lifecycle -a claude-code`. Or copy the skill folder (packages/memory/skills/judge-task-lifecycle in sno-ai/sno-station) into .claude/skills/judge-task-lifecycle in your project. Claude Code loads it when a task matches its description.
Run `npx skills add sno-ai/sno-station --skill judge-task-lifecycle -a codex`. Or copy the skill folder (packages/memory/skills/judge-task-lifecycle in sno-ai/sno-station) into .agents/skills/judge-task-lifecycle in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add sno-ai/sno-station --skill judge-task-lifecycle -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/judge-task-lifecycle, .gemini/skills/judge-task-lifecycle, .github/skills/judge-task-lifecycle and .opencode/skills/judge-task-lifecycle in your project.
SKILL.md names no scripts, command-line tools or credentials: Judge Task Lifecycle is instructions for the agent only.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
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.
Judge Task Lifecycle 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.
About 679 tokens (SKILL.md is roughly 2.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Judge Task Lifecycle: MCP Server Builder (anthropics/skills, 180k stars), Hook Development for Claude Code Plugins (anthropics/claude-plugins-official, 38k stars), Using Superpowers (farm-fe/farm, 5.6k stars) and Executing Plans Inline (obra/superpowers, 297k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
sno-ai (a GitHub organization) maintains it in sno-ai/sno-station, which has 542 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on October 11, 2026.
Source: sno-ai/sno-station on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.