<feed xmlns='http://www.w3.org/2005/Atom'>
<title>ida-tui.git/.agents, branch main</title>
<subtitle>tui for headless ida</subtitle>
<id>https://git.sl0p.foo/ida-tui.git/atom/.agents?h=main</id>
<link rel='self' href='https://git.sl0p.foo/ida-tui.git/atom/.agents?h=main'/>
<link rel='alternate' type='text/html' href='https://git.sl0p.foo/ida-tui.git/'/>
<updated>2026-08-09T20:55:38Z</updated>
<entry>
<title>Ship the idatui agent skill in-repo at .agents/skills/</title>
<updated>2026-08-09T20:55:38Z</updated>
<author>
<name>blasty</name>
<email>blasty@local</email>
</author>
<published>2026-08-09T20:55:38Z</published>
<link rel='alternate' type='text/html' href='https://git.sl0p.foo/ida-tui.git/commit/?id=90bbe6de2af245af37bfdc66796c2fa7d6dc27e0'/>
<id>urn:sha1:90bbe6de2af245af37bfdc66796c2fa7d6dc27e0</id>
<content type='text'>
Follows the Agent Skills standard (agentskills.io) rather than a contrib/
dir: harnesses discover .agents/skills/&lt;name&gt;/SKILL.md automatically from
the repo root, and it is vendor-neutral (not .claude/ or .pi/ specific).

Not a verbatim copy of the local one -- it was ~85% generic and the rest
had to go before redistributing:

  * the backend is described as a normal pyproject dependency, with the
    editable-git-checkout setup demoted to a conditional note (that is one
    maintainer's layout, but the 'upstream pull silently swaps the backend'
    warning is worth keeping for anyone who does it);
  * personal agent tooling (bgrun/waitfor wrappers) replaced by the
    underlying lesson -- a backgrounded subshell holds the inherited stdout,
    so redirect all three fds -- which is true without those scripts;
  * maintainer commit authorship dropped;
  * absolute ~/dev paths made relative to the repo root; ~/ida-venv kept but
    marked as this project's assumption, matching the README.

Also fixes the README's stale full-run count (788/~2m -&gt; 1031/~50s), lists
the docs that were missing from the index, and warns that a user-level skill
of the same name shadows this one -- otherwise a personal copy silently wins
and the in-repo copy rots.
</content>
</entry>
</feed>
