All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
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, tytso@mit.edu,
	workflows@vger.kernel.org
Subject: Re: [PATCH 0/2] agents: add portable agent skills and Fixes attribution
Date: Thu, 15 Oct 2026 09:42:49 -0400	[thread overview]
Message-ID: <atDYWe9L0tv90Xjk@laps> (raw)
In-Reply-To: <CANiq72m6okeCHuR8BCGENTw=wJhfXXZbXZtJq8xtoeVfvfo3TQ@mail.gmail.com>

On Wed, Oct 14, 2026 at 11:37:56PM +0200, Miguel Ojeda wrote:
>On Wed, Oct 14, 2026 at 7:58 PM Sasha Levin <sashal@kernel.org> 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.
>
>What I mean is that they don't get automatically picked up by default,
>e.g. Claude Code and Codex don't seem to.
>
>The website you link (in another subpage, not the spec one) mentions
>`.agents`, but not `agents` without the period.
>
>So what I wanted is just to confirm that, at least between those two
>options, there was no inherent advantage (or disadvantage, depending
>on how one sees it -- I am not sure if it is actually a good idea for
>all use cases to have them automatically be picked up...).
>
>> We can open the markup language discussion, but I'm concerned that doing that
>> will break some tools logic around importing these at skills.
>
>Hmm... Not sure what you mean.

Sorry, what I meant to say is that the spec seems to require markdown as it's
preferred format. We can experiment with other options, but then the risk is
that we'll break some tools.

-- 
Thanks,
Sasha

  reply	other threads:[~2026-10-15 13:42 UTC|newest]

Thread overview: 30+ 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
2026-10-14 21:39       ` Miguel Ojeda
2026-10-14 21:37     ` Miguel Ojeda
2026-10-15 13:42       ` Sasha Levin [this message]
2026-10-15 13:51         ` Miguel Ojeda
2026-10-15 13:57           ` Jonathan Corbet
2026-10-15 14:05             ` Miguel Ojeda
2026-10-15 14:42               ` Theodore Tso
2026-10-15 16:15                 ` Miguel Ojeda
2026-10-15 14:47             ` Sasha Levin
2026-10-15 15:34               ` Jonathan Corbet

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=atDYWe9L0tv90Xjk@laps \
    --to=sashal@kernel.org \
    --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=miguel.ojeda.sandonis@gmail.com \
    --cc=ojeda@kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=skhan@linuxfoundation.org \
    --cc=tytso@mit.edu \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.