agentation watch mode

AI Community

Skill notes

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_acknowledge immediately so the user can see you picked it up. Read any extra session context you need. Make the requested fix.

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.

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
AI
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
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 explicit requirements detected
Detected file/system behavior
  • Read-only
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

Author source file SKILL.md

# 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

1. Start a watch loop with `agentation_agentation_watch_annotations`.
2. For each returned annotation:
   - Call `agentation_agentation_acknowledge` immediately so the user can see you picked it up.
   - Read any extra session context you need.
   - Make the requested fix.
   - Call `agentation_agentation_resolve` with a short summary of what changed.
3. After the batch is done, call `agentation_agentation_watch_annotations` again.
4. 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.

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.