agent-teams-idle-state
Sub-skill of agent-teams: Idle State.
Best use case
agent-teams-idle-state is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Sub-skill of agent-teams: Idle State.
Teams using agent-teams-idle-state should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/idle-state/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How agent-teams-idle-state Compares
| Feature / Agent | agent-teams-idle-state | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Sub-skill of agent-teams: Idle State.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Idle State ## Idle State Teammates go idle after every turn — this is normal. An idle notification does NOT mean the teammate is done or unavailable. Send them a message to wake them up. Do not interpret idle as failure.
Related Skills
teams-meeting-pipeline
Operate the Teams meeting summary pipeline via Hermes CLI — summarize meetings, inspect pipeline status, replay jobs, manage Microsoft Graph subscriptions.
recover-from-corrupted-git-state
Diagnose and recover from corrupted git states (stale locks, failed rebases, pre-commit hook blocks) during bulk operations
multi-layer-stale-state-debugging
Detect and clear stale state persisting across multiple storage layers (auth files, cache, code logic)
user-approved-plan-state-sync
Reconcile GitHub and local repo state when a plan has been user-approved, including direct approval messages that require creating the local marker and moving the issue to status:plan-approved.
session-start-dirty-state-triage-with-background-agents
Distinguish real implementation dirt from generated session-state churn when resuming a repo with active overnight/background agents.
live-state-aware-overnight-implementation-prompts
Design overnight implementation prompts that begin with a live repo/CI precheck so workers continue from partial progress instead of replaying stale handoffs.
plan-rerun-review-state-sync
Keep iterative plan-review reruns truthful by syncing prompt files, canonical review artifacts, and the plan's own review-summary narrative after each adversarial wave.
plan-rerun-state-revalidation
Revalidate live plan state before rerunning adversarial review or resuming from a handoff so review prompts do not encode stale approval/artifact assumptions.
financial-statements
Generate income statements, balance sheets, and cash flow statements with GAAP presentation and period-over-period comparison.
hidden-folder-audit-verify-hidden-folder-state
Sub-skill of hidden-folder-audit: Verify Hidden Folder State (+3).
mkdocs-state-diagram
Sub-skill of mkdocs: State Diagram.
state-directory-manager-5-cache-management
Sub-skill of state-directory-manager: 5. Cache Management (+1).