Skip to content

Author the taOS OS-native agent SKILL (operate-the-OS-for-the-user) - #2283

Merged
jaylfc merged 4 commits into
devfrom
exec/tsk-36vlxg
Aug 5, 2026
Merged

Author the taOS OS-native agent SKILL (operate-the-OS-for-the-user)#2283
jaylfc merged 4 commits into
devfrom
exec/tsk-36vlxg

Conversation

@jaylfc

@jaylfc jaylfc commented Aug 4, 2026

Copy link
Copy Markdown
Owner

CARD TITLE (intent, not commit subject): Author the taOS OS-native agent SKILL (operate-the-OS-for-the-user)

Autonomous build of board card tsk-36vlxg.

Add .claude/skills/taos-agent/SKILL.md consolidating the agent-manual
OS-operation content into actionable instructions for the OS-native taOS
agent. Features the hard rule that all desktop driving goes only through
POST /api/desktop/command + POST /api/desktop/screenshot. Covers opening
and driving apps and windows, desktop control, projects, files, memory and
notes, chat conventions, image generation, and answering the user.

Updates docs/agent-manual/index.md to point at the new skill and at the
existing taos-development-skill. Adds a CHANGELOG entry.

Draft for @taOS-dev review.

Files:
.claude/skills/taos-agent/SKILL.md | 399 +++++++++++++++++++++++++++++++++++++
CHANGELOG.md | 8 +
docs/agent-manual/index.md | 12 ++
3 files changed, 419 insertions(+)

Summary by CodeRabbit

  • Documentation
    • Added comprehensive guidance for the taOS agent, covering desktop control, app and window management, project workflows, memory, privacy, troubleshooting, and response conventions.
    • Updated the agent manual with companion skill references and usage scopes.
  • Changelog
    • Added an unreleased entry documenting the new taOS agent skill and related manual updates.

@gitar-bot

gitar-bot Bot commented Aug 4, 2026

Copy link
Copy Markdown

Gitar is working

Gitar

@coderabbitai

coderabbitai Bot commented Aug 4, 2026

Copy link
Copy Markdown

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 99e0a6c9-8b88-4ae3-83a0-d47a14319111

📥 Commits

Reviewing files that changed from the base of the PR and between 41dce53 and 93ed552.

📒 Files selected for processing (1)
  • docs/agent-manual/index.md
🚧 Files skipped from review as they are similar to previous changes (1)
  • docs/agent-manual/index.md

📝 Walkthrough

Walkthrough

Added the taos-agent skill documentation with desktop-control, project, file, communication, image-generation, update, privacy, and safety instructions. Updated the agent manual index and unreleased changelog.

Changes

taos-agent documentation

Layer / File(s) Summary
taos-agent control and workflow definition
.claude/skills/taos-agent/SKILL.md
Defines desktop-control requirements, taOS product details, application and window workflows, and project and file operations.
Agent interaction and safety rules
.claude/skills/taos-agent/SKILL.md
Defines memory, messaging, image-generation, response, update, privacy, and prohibited-action guidance.
Documentation indexing and changelog
docs/agent-manual/index.md, CHANGELOG.md
Adds companion-skill links to the agent manual and documents the new skill in the unreleased changelog.

Estimated code review effort: 2 (Simple) | ~10 minutes

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly identifies the primary change: adding the taOS OS-native agent skill.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch exec/tsk-36vlxg

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@qodo-code-review

Copy link
Copy Markdown

PR Summary by Qodo

Add taos-agent SKILL docs for OS-native desktop operation via control API

📝 Documentation 🕐 20-40 Minutes

Grey Divider

AI Description

• Add a new taos-agent skill document for OS-native desktop operation.
• Codify the hard rule: drive the desktop only via /api/desktop/command + screenshots/layout.
• Link the agent manual index and changelog to the new skill and existing dev skill.
Diagram

sequenceDiagram
  participant Agent as "taOS agent"
  participant API as "Desktop control API"
  participant Desktop as "Browser desktop"
  participant Apps as "App/window receivers"
  participant Result as "Result endpoints"
  Desktop->>API: "GET /api/desktop/stream" (SSE subscribe)
  Agent->>API: "POST /api/desktop/command" (open-app/window)
  API-->>Desktop: "command" event
  Desktop-->>Apps: "taos:open-app" / "taos:window"
  Agent->>API: "POST /api/desktop/screenshot" or "/api/desktop/layout"
  API-->>Desktop: "screenshot" / "layout" request
  Desktop->>Result: "POST /api/desktop/screenshot-result" or "/api/desktop/layout-result"
  Result-->>Agent: "PNG" / "layout JSON"
Loading
High-Level Assessment

The following are alternative approaches to this PR:

1. Generate SKILL.md from agent-manual sources
  • ➕ Eliminates drift between docs/agent-manual/* and the skill
  • ➕ Keeps a single source of truth while still shipping the skill file
  • ➕ Makes future edits smaller (edit source docs; regenerate)
  • ➖ Requires adding/maintaining a small build step and ensuring it runs in CI
  • ➖ Harder to do one-off edits to the skill without updating sources
2. Keep only the agent manual and link to it (no separate skill)
  • ➕ Avoids duplicating content across two documentation entrypoints
  • ➕ No additional file to maintain
  • ➖ Less actionable for an OS-native agent prompt/skill loader that expects a dedicated SKILL document
  • ➖ Harder to enforce the “hard rule” prominently at the top in the skill context

Recommendation: The current approach (a dedicated taos-agent SKILL that consolidates OS-operation rules) is appropriate for an OS-native agent because it centralizes the operational contract (especially the control-API hard rule) in a loadable format. If this content will evolve rapidly, consider a follow-up that generates the SKILL from docs/agent-manual/ sources to prevent documentation drift.

Files changed (3) +419 / -0

Documentation (3) +419 / -0
SKILL.mdAdd OS-native taOS agent skill (desktop control + user-facing conventions) +399/-0

Add OS-native taOS agent skill (desktop control + user-facing conventions)

• Introduces a new 'taos-agent' skill document describing how the OS-native agent should operate the host desktop. Codifies the hard rule to drive all desktop actions through 'POST /api/desktop/command' and read state via screenshot/layout endpoints, and documents app usage, window control, projects/files/memory/notes, chat conventions, image prompting, and answer templates.

.claude/skills/taos-agent/SKILL.md

CHANGELOG.mdChangelog entry for new taos-agent OS skill documentation +8/-0

Changelog entry for new taos-agent OS skill documentation

• Adds an Unreleased changelog bullet announcing the new 'taos-agent' skill and summarizes its scope and the control-API hard rule emphasis.

CHANGELOG.md

index.mdLink agent manual to companion skills (taos-agent + taos-development-skill) +12/-0

Link agent manual to companion skills (taos-agent + taos-development-skill)

• Adds a “Companion skills” section pointing readers to the new OS-native 'taos-agent' skill and the existing 'taos-development-skill', clarifying when each should be used.

docs/agent-manual/index.md

@jaylfc

jaylfc commented Aug 4, 2026

Copy link
Copy Markdown
Owner Author

nemotron-super review

VERDICT: No blocking issues found.

  • No blocking issues found.

Automated first-pass review by the nemotron-super lane. The lead still reviews before merge.

@jaylfc

jaylfc commented Aug 4, 2026

Copy link
Copy Markdown
Owner Author

Reviewed at 5dc275f; one clarification added by me at 67130a3. Good build, and it shipped WITH a changelog line unprompted - noting that, since every other lane PR today needed one added.

VERIFIED, because a skill doc is executable in practice - agents act on it, so an inaccurate one is worse than none:

  • Replay check clean: one commit on the current dev tip, files match the card.
  • EVERY endpoint it teaches exists: all of /api/desktop/{command,layout,screenshot,stream} resolve in routes/desktop_control.py, and all of /api/projects/{slug}/{files,files/upload,mkdir,stats} in routes/project_files.py. Checked each, not sampled.
  • Both scopes it names (files_read, files_write) are real entries in _ALLOWED_SCOPES.
  • No collision: taos-development-skill is the only existing skill and this one has a distinct purpose (operate the OS for the user, vs contribute to the repo).

ADDED, the one real gap: the doc told agents to drive /api/desktop/* without saying that a registry JWT cannot reach it. Verified in auth_middleware.py - /api/desktop/* appears in NO agent-bearer passthrough list (feeds, A2A, observatory, tasks, doc-review, canvas, decisions, files, scope-requests), and desktop_control scopes by request.state.user_id, which the middleware deliberately leaves unset for registry tokens. Meanwhile the files section immediately below DOES tell agents to use a registry JWT, so the natural reading is that the same bearer works for both. It does not, and an agent following this would have burned turns on 401s before working that out. Now stated explicitly, with the contrast to the files routes.

Docs-only, +419/-0. Auto-merge armed on green.

@jaylfc
jaylfc enabled auto-merge (squash) August 4, 2026 08:00
@qodo-code-review

Copy link
Copy Markdown

Code Review by Qodo

🐞 Bugs (2) 📘 Rule violations (0) 📜 Skill insights (0)

Context used
✅ Compliance rules (platform): 35 rules

Grey Divider


Action required

1. Wrong install command URL 🐞 Bug ≡ Correctness
Description
.claude/skills/taos-agent/SKILL.md instructs agents to quote an install command that fetches
install-server.sh from jaylfc/tinyagentos, but the installer in this repo (and README) point to
jaylfc/taOS. Users copy/pasting the documented command may hit a 404 or install from an unintended
upstream.
Code

.claude/skills/taos-agent/SKILL.md[R81-82]

+Install command (quote exactly):
+`curl -fsSL https://raw.githubusercontent.com/jaylfc/tinyagentos/master/scripts/install-server.sh | sudo bash`
Relevance

●●● Strong

Team often accepts doc command corrections to prevent copy/paste breakage; install/script accuracy
is prioritized.

PR-#482
PR-#1294

ⓘ Recommendations generated based on similar findings in past PRs

Evidence
SKILL.md hard-codes the installer download URL as jaylfc/tinyagentos, while both the actual
installer script and README document jaylfc/taOS as the canonical source; these can’t both be
correct for copy/paste installs.

.claude/skills/taos-agent/SKILL.md[81-83]
scripts/install-server.sh[8-20]
README.md[465-468]

Agent prompt
The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

### Issue description
The new taos-agent skill tells the OS-native agent to quote an install command that downloads the installer script from the wrong GitHub repository (`jaylfc/tinyagentos`). The installer script in this repo (and README) indicate the canonical source is `jaylfc/taOS`.

### Issue Context
This is explicitly marked as “quote exactly”, so a wrong URL is a high-impact copy/paste break.

### Fix Focus Areas
- .claude/skills/taos-agent/SKILL.md[81-83]
- scripts/install-server.sh[8-20]
- README.md[465-468]

### Expected fix
Update the SKILL.md install command to match the canonical raw URL used by `scripts/install-server.sh` / README (currently `https://raw.githubusercontent.com/jaylfc/taOS/master/scripts/install-server.sh`).

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools


2. Upload conflict contract wrong 🐞 Bug ≡ Correctness
Description
.claude/skills/taos-agent/SKILL.md claims /api/projects/{slug}/files/upload returns 400 on
conflicts, but the server implementation writes the destination file unconditionally (overwriting if
it already exists). Agents following the documented contract may inadvertently clobber existing
project files.
Code

.claude/skills/taos-agent/SKILL.md[R197-200]

+- `POST /api/projects/{slug}/files/upload?path=<subdir>` -- multipart form field `file`.
+  Returns `{name, path, size, status}`. `?path=` places it in a subfolder; a conflict is
+  a 400. Needs `files_write`.
+- `POST /api/projects/{slug}/mkdir` -- JSON `{"path": "<subdir>"}`. Needs `files_write`.
Relevance

●●● Strong

Doc/API contract mismatches are typically fixed to avoid unsafe behavior; similar doc-correctness
fixes were accepted.

PR-#482

ⓘ Recommendations generated based on similar findings in past PRs

Evidence
SKILL.md states conflicts return 400, but api_project_upload_file writes
dest.write_bytes(content) without checking whether dest already exists, so same-name uploads
overwrite instead of failing.

.claude/skills/taos-agent/SKILL.md[197-203]
tinyagentos/routes/project_files.py[204-229]

Agent prompt
The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

### Issue description
The taos-agent skill documents that `POST /api/projects/{slug}/files/upload` returns a 400 on conflicts. The current route implementation does not check for an existing destination filename and will overwrite.

### Issue Context
This skill is intended to drive agent behavior. A mismatch here can lead to silent data loss when an agent uploads a file with an existing name.

### Fix Focus Areas
- .claude/skills/taos-agent/SKILL.md[197-203]
- tinyagentos/routes/project_files.py[204-229]

### Expected fix
Pick one and make docs+code consistent:
1) **Doc fix (simplest):** Update SKILL.md to explicitly state that upload overwrites an existing file of the same name (and only errors on invalid path / path conflicts where `path` targets a file).
2) **Behavior fix (safer):** Add a destination-exists check (ideally race-safe) and return a conflict error (400/409), optionally adding an explicit overwrite flag/query param if overwrites are desired sometimes.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools


Grey Divider

To customize comments, go to the Qodo configuration screen, or learn more in the docs.

Qodo Logo

Comment on lines +81 to +82
Install command (quote exactly):
`curl -fsSL https://raw.githubusercontent.com/jaylfc/tinyagentos/master/scripts/install-server.sh | sudo bash`

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Action required

1. Wrong install command url 🐞 Bug ≡ Correctness

.claude/skills/taos-agent/SKILL.md instructs agents to quote an install command that fetches
install-server.sh from jaylfc/tinyagentos, but the installer in this repo (and README) point to
jaylfc/taOS. Users copy/pasting the documented command may hit a 404 or install from an unintended
upstream.
Agent Prompt
### Issue description
The new taos-agent skill tells the OS-native agent to quote an install command that downloads the installer script from the wrong GitHub repository (`jaylfc/tinyagentos`). The installer script in this repo (and README) indicate the canonical source is `jaylfc/taOS`.

### Issue Context
This is explicitly marked as “quote exactly”, so a wrong URL is a high-impact copy/paste break.

### Fix Focus Areas
- .claude/skills/taos-agent/SKILL.md[81-83]
- scripts/install-server.sh[8-20]
- README.md[465-468]

### Expected fix
Update the SKILL.md install command to match the canonical raw URL used by `scripts/install-server.sh` / README (currently `https://raw.githubusercontent.com/jaylfc/taOS/master/scripts/install-server.sh`).

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

Comment on lines +197 to +200
- `POST /api/projects/{slug}/files/upload?path=<subdir>` -- multipart form field `file`.
Returns `{name, path, size, status}`. `?path=` places it in a subfolder; a conflict is
a 400. Needs `files_write`.
- `POST /api/projects/{slug}/mkdir` -- JSON `{"path": "<subdir>"}`. Needs `files_write`.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Action required

2. Upload conflict contract wrong 🐞 Bug ≡ Correctness

.claude/skills/taos-agent/SKILL.md claims /api/projects/{slug}/files/upload returns 400 on
conflicts, but the server implementation writes the destination file unconditionally (overwriting if
it already exists). Agents following the documented contract may inadvertently clobber existing
project files.
Agent Prompt
### Issue description
The taos-agent skill documents that `POST /api/projects/{slug}/files/upload` returns a 400 on conflicts. The current route implementation does not check for an existing destination filename and will overwrite.

### Issue Context
This skill is intended to drive agent behavior. A mismatch here can lead to silent data loss when an agent uploads a file with an existing name.

### Fix Focus Areas
- .claude/skills/taos-agent/SKILL.md[197-203]
- tinyagentos/routes/project_files.py[204-229]

### Expected fix
Pick one and make docs+code consistent:
1) **Doc fix (simplest):** Update SKILL.md to explicitly state that upload overwrites an existing file of the same name (and only errors on invalid path / path conflicts where `path` targets a file).
2) **Behavior fix (safer):** Add a destination-exists check (ideally race-safe) and return a conflict error (400/409), optionally adding an explicit overwrite flag/query param if overwrites are desired sometimes.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

jaylfc added 2 commits August 4, 2026 11:15
Add .claude/skills/taos-agent/SKILL.md consolidating the agent-manual
OS-operation content into actionable instructions for the OS-native taOS
agent. Features the hard rule that all desktop driving goes only through
POST /api/desktop/command + POST /api/desktop/screenshot. Covers opening
and driving apps and windows, desktop control, projects, files, memory and
notes, chat conventions, image generation, and answering the user.

Updates docs/agent-manual/index.md to point at the new skill and at the
existing taos-development-skill. Adds a CHANGELOG entry.

Draft for @taOS-dev review.
| Agent frameworks | OpenClaw (default), Hermes, SmolAgents, Langroid, PocketFlow, OpenAI Agents SDK |
| Memory system | taOSmd, long-term memory shared by all agents |
| Community | github.com/jaylfc/tinyagentos/discussions |
| Bug reports | github.com/jaylfc/tinyagentos/issues |

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

WARNING: Bug reports URL uses wrong repository — tinyagentos should be taOS

The Key Facts table tells agents to direct users to github.com/jaylfc/tinyagentos/issues for bug reports, but this repo is jaylfc/taOS. An agent following this would send users to a non-canonical or wrong repository.

Suggested change
| Bug reports | github.com/jaylfc/tinyagentos/issues |
| Bug reports | github.com/jaylfc/taOS/issues |

Reply with @kilocode-bot fix it to have Kilo Code address this issue.

**Keep first answers under 6 sentences.** DO give the exact menu path or command when
one exists. DO NOT promise dates or features that are not in this skill. If you do not
know, say exactly: "I'm not sure about that one. The community page at
github.com/jaylfc/tinyagentos/discussions is the best place to ask, and bugs go to

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

WARNING: Bug reports URL uses wrong repository — tinyagentos should be taOS

The canned answer for "Where do I report a bug?" sends users to github.com/jaylfc/tinyagentos/issues, but the canonical repo is jaylfc/taOS.

Suggested change
github.com/jaylfc/tinyagentos/discussions is the best place to ask, and bugs go to
**"Where do I report a bug?"** -- github.com/jaylfc/taOS/issues, with the error

Reply with @kilocode-bot fix it to have Kilo Code address this issue.

memory, settings). Settings has a backups section; copying the whole data directory
while taOS is stopped is also a complete backup.

**"Where do I report a bug?"** -- github.com/jaylfc/tinyagentos/issues, with the error

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

WARNING: Bug reports URL uses wrong repository — tinyagentos should be taOS

Same wrong URL appears in the explicit answer shape. Agents quoting this would direct users to the wrong repo.

Suggested change
**"Where do I report a bug?"** -- github.com/jaylfc/tinyagentos/issues, with the error
text and what hardware you are on.

Reply with @kilocode-bot fix it to have Kilo Code address this issue.

**before** reasoning from scratch:

- In the repo: `docs/UPDATE_BREAKAGE_LOG.md`
- Latest online: `https://raw.githubusercontent.com/jaylfc/tinyagentos/master/docs/UPDATE_BREAKAGE_LOG.md`

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

WARNING: UPDATE_BREAKAGE_LOG URL uses wrong repository — tinyagentos should be taOS

The "After an update" section points agents to https://raw.githubusercontent.com/jaylfc/tinyagentos/master/docs/UPDATE_BREAKAGE_LOG.md, but the canonical repo is jaylfc/taOS.

Suggested change
- Latest online: `https://raw.githubusercontent.com/jaylfc/tinyagentos/master/docs/UPDATE_BREAKAGE_LOG.md`
- Latest online: `https://raw.githubusercontent.com/jaylfc/taOS/master/docs/UPDATE_BREAKAGE_LOG.md`

Reply with @kilocode-bot fix it to have Kilo Code address this issue.

> `request.state.user_id`, which the middleware deliberately leaves unset for registry
> tokens. A `Authorization: Bearer <registry JWT>` call here is rejected, unlike the
> project-files routes below, which ARE agent-reachable with `files_read`/`files_write`.
> Drive the desktop from the in-OS agent's session; do not retry with an agent token. The browser subscribes over

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

WARNING: Blockquote and following paragraph are merged without a blank line — creates a run-on sentence

The blockquote closes mid-line and The browser subscribes over starts immediately after it on the same line with no blank-line break. Markdown renders this as a continuation of the blockquote, making it read as one long, awkward sentence.

Suggested change
> Drive the desktop from the in-OS agent's session; do not retry with an agent token. The browser subscribes over
> Drive the desktop from the in-OS agent's session; do not retry with an agent token.
>
The browser subscribes over

Reply with @kilocode-bot fix it to have Kilo Code address this issue.

@kilo-code-bot

kilo-code-bot Bot commented Aug 4, 2026

Copy link
Copy Markdown

Code Review Summary

Status: No Issues Found | Recommendation: Merge

Files Reviewed (1 file)
  • docs/agent-manual/index.md
Previous Review Summaries (2 snapshots, latest commit a938952)

Current summary above is authoritative. Previous snapshots are kept for context only.

Previous review (commit a938952)

Status: 5 Issues Found | Recommendation: Address before merge

Overview

Severity Count
WARNING 5
Issue Details (click to expand)

WARNING

File Line Issue
.claude/skills/taos-agent/SKILL.md 86 Bug reports URL uses github.com/jaylfc/tinyagentos/issues instead of github.com/jaylfc/taOS/issues (Key Facts table)
.claude/skills/taos-agent/SKILL.md 317 Bug reports URL uses github.com/jaylfc/tinyagentos/issues instead of github.com/jaylfc/taOS/issues (answer shape)
.claude/skills/taos-agent/SKILL.md 355 Bug reports URL uses github.com/jaylfc/tinyagentos/issues instead of github.com/jaylfc/taOS/issues (answer shape)
.claude/skills/taos-agent/SKILL.md 391 UPDATE_BREAKAGE_LOG URL uses raw.githubusercontent.com/jaylfc/tinyagentos instead of jaylfc/taOS
.claude/skills/taos-agent/SKILL.md 46 Blockquote runs directly into the following sentence without a blank-line break, producing a run-on in rendered Markdown
Files Reviewed (3 files)
  • .claude/skills/taos-agent/SKILL.md — 5 issues (2 pre-existing by qodo-code-review[bot] on lines 89, 207; 5 new)
  • CHANGELOG.md
  • docs/agent-manual/index.md

Fix these issues in Kilo Cloud

Previous review (commit 41dce53)

Status: 5 Issues Found | Recommendation: Address before merge

Overview

Severity Count
WARNING 5
Issue Details (click to expand)

WARNING

File Line Issue
.claude/skills/taos-agent/SKILL.md 86 Bug reports URL uses github.com/jaylfc/tinyagentos/issues instead of github.com/jaylfc/taOS/issues (Key Facts table)
.claude/skills/taos-agent/SKILL.md 317 Bug reports URL uses github.com/jaylfc/tinyagentos/issues instead of github.com/jaylfc/taOS/issues (answer shape)
.claude/skills/taos-agent/SKILL.md 355 Bug reports URL uses github.com/jaylfc/tinyagentos/issues instead of github.com/jaylfc/taOS/issues (answer shape)
.claude/skills/taos-agent/SKILL.md 391 UPDATE_BREAKAGE_LOG URL uses raw.githubusercontent.com/jaylfc/tinyagentos instead of jaylfc/taOS
.claude/skills/taos-agent/SKILL.md 46 Blockquote runs directly into the following sentence without a blank-line break, producing a run-on in rendered Markdown
Files Reviewed (3 files)
  • .claude/skills/taos-agent/SKILL.md — 5 issues (2 pre-existing by qodo-code-review[bot] on lines 89, 207; 5 new)
  • CHANGELOG.md
  • docs/agent-manual/index.md

Fix these issues in Kilo Cloud


Reviewed by step-3.7-flash · Input: 33.2K · Output: 1.2K · Cached: 140K

jaylfc added 2 commits August 4, 2026 16:11
doc-gate's failure was recorded at 11:16Z against the PREVIOUS head; the rebase
at 41dce53 landed after it and doc-gate never re-reported, leaving a stale
required check blocking the PR. Verified clean locally against current dev.
…ading it as a path

check_doc_gate.py's Layer A scans index.md for referenced repo paths and treated
the slash in 'desktop/window control' as a path that does not exist. It is
prose, not a path. 'desktop and window control' reads better anyway.
@jaylfc
jaylfc merged commit 94cbb74 into dev Aug 5, 2026
18 of 19 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant