agentation-watch-mode
- Repo stars 4,024
- Author updated Live
- Author repo latitude-llm
- Domain
- AI
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- Author / version / license
- @latitude-dev · no license declared
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No special requirements
- Permissions
-
- Read-only
- Write / modify
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools，默认拥有全部工具权限。
---
name: agentation-watch-mode
description: Continuous Agentation annotation handling. Use when the user says "watch mode", asks you to watc…
category: ai
runtime: no special runtime
---
# agentation-watch-mode output preview
## PART A: Task fit
- Use case: Continuous Agentation annotation handling. Use when the user says "watch mode", asks you to watch for Agentation annotations, process feedback as it arrives, or keep fixing annotation-driven changes until told to stop or a timeout is reached..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Goal / Workflow / Defaults” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Continuous Agentation annotation handling. Use when the user says "watch mode", asks you to watch for Agentation annotations, process feedback as it arrives, or keep fixing annotation-driven changes until told to stop or a timeout is reached.”.
- **02** When the source has headings, the agent prioritizes “Goal / Workflow / Defaults” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. Choose the trigger
The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Provide inputs and boundaries
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files.
Validate with a small run
Start with a small task and check whether the result follows “Goal / Workflow / Defaults”. Inspect diffs, logs, previews, or tests before expanding scope.
Review before delivery
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: agentation-watch-mode
description: Continuous Agentation annotation handling. Use when the user says "watch mode", asks you to watc…
category: ai
source: latitude-dev/latitude-llm
---
# agentation-watch-mode
## When to use
- Continuous Agentation annotation handling. Use when the user says "watch mode", asks you to watch for Agentation annot…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Goal / Workflow / Defaults” and keep inference separate from source facts.
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. Evidence boundary and execution chain
The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "agentation-watch-mode" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Goal / Workflow / Defaults
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, write/modify files | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
}Agentation watch mode
When to use: The user says watch mode, wants continuous Agentation feedback handling, or asks you to keep watching annotations and applying fixes as new feedback arrives.
Goal
Stay in a watch loop so the user can annotate in the browser and have those annotations processed continuously.
Workflow
- Start a watch loop with
agentation_agentation_watch_annotations. - For each returned annotation:
- Call
agentation_agentation_acknowledgeimmediately so the user can see you picked it up. - Read any extra session context you need.
- Make the requested fix.
- Call
agentation_agentation_resolvewith a short summary of what changed.
- Call
- After the batch is done, call
agentation_agentation_watch_annotationsagain. - Continue until the user says stop or the watch call times out.
Defaults
- If the user gives a session ID, watch that session.
- If they do not, watch all sessions.
- Use a short batching window so nearby annotations are grouped together.
- Use a reasonable timeout and report when it expires.
Handling ambiguous feedback
- If an annotation is unclear, reply on the thread with a short clarifying question before making speculative changes.
- If you cannot complete the fix safely, leave the annotation open and explain the blocker in a reply.
Response style
- Keep progress updates brief.
- In each resolve summary, state what you changed, not just that it is done.
Decide Fit First
Design Intent
How To Use It
Boundaries And Review