//
sign in
Profile
by @danabra.mov
Profile
by @dansshadow.bsky.social
Profile
by @jimpick.com
AviHandle
by @danabra.mov
AviHandle
by @dansshadow.bsky.social
AviHandle
by @katherine.computer
EventsList
by @katherine.computer
ProfileHeader
by @dansshadow.bsky.social
ProfileHeader
by @danabra.mov
ProfileMedia
by @danabra.mov
ProfilePlays
by @danabra.mov
ProfilePosts
by @danabra.mov
ProfilePosts
by @dansshadow.bsky.social
ProfileReplies
by @danabra.mov
Record
by @atsui.org
Skircle
by @danabra.mov
StreamPlacePlaylist
by @katherine.computer
+ new component
ProfileReplies









Loading...
Great news if this is true? Free? Hopefully won’t need to worry about using my copilot tokens? x.com/israfill/sta...
That’s true. I attach the video content to the article so if there’s enough info in the article to interest me then I’ll watch the video. We also don’t get the slides. Perhaps I need to scrape the meta data to see if they include a link
Succinctly put and totally agree
I’m thinking with my own code of having the plugin provide ootb skill like ‘mvn dependency:install-skill’ . Is this madness or is it better to let others build their own? I see a lot of people not engaging with skills and the like so they won’t get these nice touches until the models have the data
Nice feature. How are you going about getting this approach into your agents? A maven dependency skill? I have something similar to look up latest version when adding a dependency. Feels like more of these plugins need a way we can keep our agents up to date with their features and usage
I was tired of rebuilding the same Copilot setup for every new repo. So I created my own ai-toolkit: versioned bundles of prompts, agents, skills and instructions, installable via JBang in minutes. jbang AiToolkit.java install discovery robintegg.com/2026/05/24/c...
Discovery before planning is now default in my AI workflow. Load context, run discovery, write plan, implement. Simple and repeatable. My May 2026 AI retrospective: robintegg.com/2026/06/01/m...