From: "Theodore Tso" <tytso@mit.edu>
To: Sasha Levin <sashal@kernel.org>
Cc: Miguel Ojeda <ojeda@kernel.org>,
broonie@kernel.org, corbet@lwn.net, ksummit@lists.linux.dev,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
rdunlap@infradead.org, skhan@linuxfoundation.org,
workflows@vger.kernel.org
Subject: Re: [PATCH 0/2] agents: add portable agent skills and Fixes attribution
Date: Wed, 14 Oct 2026 16:28:07 -0400 [thread overview]
Message-ID: <as_j3DawEZQWA4ls@mit.edu> (raw)
In-Reply-To: <as_Cr4FhzyAh-kC4@laps>
On Wed, Oct 14, 2026 at 01:58:07PM -0500, Sasha Levin wrote:
> I'm following the specs[1] for these skills, and my testing showed it works
> fine with a few of the more common tools.
>
> We can open the markup language discussion, but I'm concerned that doing that
> will break some tools logic around importing these at skills.
Most modern LLM's can deal with .md, .rst, .txt, and even .html
(although I don't recommend HTML mostly because it's more
token-inefficient and it's easier to insert prompt-injection attacks
in the form of 1 point text that is a lot harder for humans to notice).
> This was one of the reasons I sent the first version as agents/ rather than
> something under Documentation/ - this really feels like coding in English vs
> writing docs for humans :)
My preference is agents/ because these skills really aren't docs at
all. This is especially true if some of future skills invoke python
scripts.
- Ted
next prev parent reply other threads:[~2026-10-14 20:29 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-08 22:54 [PATCH 0/2] agents: add portable agent skills and Fixes attribution Sasha Levin
2026-10-08 22:54 ` [PATCH 1/2] agents: add infrastructure for agent resources Sasha Levin
2026-10-09 10:27 ` Greg KH
2026-10-09 10:35 ` Sasha Levin
2026-10-09 10:53 ` Greg KH
2026-10-09 13:40 ` Leon Romanovsky
2026-10-09 14:20 ` Sasha Levin
2026-10-09 14:22 ` Konstantin Ryabitsev
2026-10-09 16:36 ` Leon Romanovsky
2026-10-09 22:28 ` Konstantin Ryabitsev
2026-10-08 22:54 ` [PATCH 2/2] agents: add a skill to determine Fixes tags Sasha Levin
2026-10-10 9:40 ` Thorsten Leemhuis
2026-10-10 10:33 ` Michael S. Tsirkin
2026-10-10 13:45 ` Sasha Levin
2026-10-09 9:42 ` [PATCH 0/2] agents: add portable agent skills and Fixes attribution Laurent Pinchart
2026-10-09 10:11 ` Sasha Levin
2026-10-09 16:30 ` Theodore Tso
2026-10-14 17:48 ` Miguel Ojeda
2026-10-14 17:58 ` Sasha Levin
2026-10-14 20:28 ` Theodore Tso [this message]
2026-10-14 21:39 ` Miguel Ojeda
2026-10-14 21:37 ` Miguel Ojeda
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=as_j3DawEZQWA4ls@mit.edu \
--to=tytso@mit.edu \
--cc=broonie@kernel.org \
--cc=corbet@lwn.net \
--cc=ksummit@lists.linux.dev \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ojeda@kernel.org \
--cc=rdunlap@infradead.org \
--cc=sashal@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=workflows@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox