keel-session
Maintains operational consistency in KEEL environments by refreshing session context.
Install
mkdir -p .claude/skills/keel-session && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/13482" && unzip -o skill.zip -d .claude/skills/keel-session && rm skill.zipInstalls to .claude/skills/keel-session
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Use this skill when working in a KEEL-managed repository and you need to re-enter the current slice cleanly.Key capabilities
- →Read session alerts
- →Read current brief
- →Run `keel watch`
- →Run `keel next`
- →Run `keel checkpoint`
- →Run `keel validate`
How it works
The skill reads session alerts and briefs, then uses `keel` commands to manage the development flow and validate changes.
Inputs & outputs
When to use keel-session
- →Re-enter active coding slice
- →Validate current drift status
- →Refresh KEEL project brief
About this skill
KEEL Session
Use this skill when working in a KEEL-managed repository and you need to re-enter the current slice cleanly.
Workflow
- Read
.keel/session/alerts.yamlfirst when it exists, then.keel/session/current-brief.md. - Run
keel watch --once --mode autoif the brief or alert feed looks stale or incomplete. - Run
keel nextbefore starting a new change slice. - If current work no longer matches the brief, use
keel checkpointorkeel replan. - When staying in the repo for a while, keep
keel watchrunning in another terminal. - After a meaningful slice, run
keel validate,keel drift --mode auto, andkeel check.
Rules
- Treat active KEEL alerts as the highest-signal short-term warning feed.
- If changed files do not map to the active goal or step, assume drift until proven otherwise.
- Keep out-of-scope items and constraints stable unless KEEL artifacts are updated.
When not to use it
- →When the repository is not managed by KEEL
- →When current work matches the brief and no new change slice is starting
Limitations
- →Requires a KEEL-managed repository
- →Assumes drift if changed files do not map to the active goal or step
How it compares
This workflow uses specific `keel` commands to manage session state, unlike manually checking repository status.
Compared to similar skills
keel-session side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| keel-session (this skill) | 0 | 4mo | No flags | Beginner |
| resolve-conflicts | 81 | 8mo | Review | Intermediate |
| openspec-onboard | 10 | 6mo | Review | Beginner |
| codex-cli-bridge | 9 | 9mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by vzwjustin
View all by vzwjustin →You might also like
resolve-conflicts
antinomyhq
Use this skill immediately when the user mentions merge conflicts that need to be resolved. Do not attempt to resolve conflicts directly - invoke this skill first. This skill specializes in providing a structured framework for merging imports, tests, lock files (regeneration), configuration files, and handling deleted-but-modified files with backup and analysis.
openspec-onboard
studyzy
Guided onboarding for OpenSpec - walk through a complete workflow cycle with narration and real codebase work.
codex-cli-bridge
alirezarezvani
Bridge between Claude Code and OpenAI Codex CLI - generates AGENTS.md from CLAUDE.md, provides Codex CLI execution helpers, and enables seamless interoperability between both tools
skill-sync
KyleKing
Syncs Claude Skills with other AI coding tools like Cursor, Copilot, and Codeium by creating cross-references and shared knowledge bases. Invoke when user wants to leverage skills across multiple tools or create unified AI context.
github-workflow-automation
ruvnet
Advanced GitHub Actions workflow automation with AI swarm coordination, intelligent CI/CD pipelines, and comprehensive repository management
git-advanced-workflows
wshobson
Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues.