Is there a way to implement skills with Gemini?
Readit NewsohghiZai commented on Show HN: AlgoDrill – Interactive drills to stop forgetting LeetCode patterns algodrill.io... · Posted by u/henwfan
Is there any way to try it without signing in via Google?
I’d sign up if there’s a way to not use Google sign in.
ohghiZai commented on Kagi Assistant is now available to all users blog.kagi.com/assistant-f... · Posted by u/angilr
How do I get this to work? When I try to access the Assistant I just get the help page: https://help.kagi.com/kagi/ai/assistant.html
Outside the US as well. You can get it to work now through a VPN. Not all models are available at the moment.
Deleted Comment
I had some trouble migrating from Poetry to uv because the dependency constraints are different. With Poetry, you can use caret ^ and tilde ~ version constraints. Apparently this is outside the PEP spec so uv doesn't implement it. Understandable, but it does make the migration a bit troublesome at times.
PEP440 and uv support ~= versioning [0], it’s a little different to Poetry’s caret specifier which is outside the spec.
ohghiZai commented on Show HN: Just Ship, a free and open source SvelteKit SaaS boilerplate justship.today/... · Posted by u/fulco__
The component library used is shadcn-svelte where you can find a dashboard and examples from here: https://www.shadcn-svelte.com/
This is not about a component library but setting up the database, orm, login, flow etc. People are selling these kind templates for 200 bucks at the moment (e.g https://shipfa.st/) so I'd thought people would enjoy it if I released mine for free.
Yeah I just checked out a few others, so I definitely appreciate your work!
Starred, will try out soon!
ohghiZai commented on Show HN: Linen.team – A lightweight, thread-first Slack alternative · Posted by u/cheeseblubber
Is there a way for automations to post messages with web hooks? That's usually the easiest automation-type feature to implement on the platform and for users
Dead Comment
My favorite manifestation to date of Emacs file handling is that if I use emacs to edit a post in my Hugo-managed site, and Emacs decides to leave one of its .#filename symlinks around that don't point to anything, hugo gets an error reading the directory and decides the entire directory is busted and doesn't read it in. So suddenly entire years of my blog start disappearing.
Granted, hugo is handling this particularly gracelessly, but it's not the only thing that gets confused and upset by the dangling symlinks that point nowhere.
Avoid committing the # tempfiles or saving them in a separate directory generally solves this problem.
1. A top level agent/custom prompt
2. Subagents that the main agent knows about via short descriptions
3. Subagents have reference files
4. Subagents have scripts
Anthropic specific implementation:
1. Skills are defined in a filesystem in a /skills folder with a specific subfolder structure of /references and /scripts.
2. Mostly designed to be run via their CLI tool, although there's a clunky way of uploading them to the web interface via zip files.
I don't think the folder structure is a necessary part of skills. I predict that if we stop looking at that, we'll see a lot of "skills-like" implementations. The scripting part is only useful for people who need to run scripts, which, aside from the now built in document manipulating scripts, isn't most people.
For example, I've been testing out Gemini Enterprise for use by staff in various (non-technical) positions at my business.
It's got the best implementation of a "skills-like" agent tool I've seen. Basically a visual tree builder, currently only one level deep. So I've set up the "<my company name> agent" and then it has subagents/skills for thing like marketing/supply chain research/sysadmin/translation etc., each with a separate description, prompt, and knowledge base, although no custom scripts.
Unfortunately, everything else about Gemini Enterprise screams "early alpha, why the hell are you selling this as an actual finished product?".
For example, after I put half a day into setting up an agent and subagents, then went to share this with the other people helping me to test it, I found that... I can't. Literally no way to share agents in a tool that is supposedly for teams to use. I found one of the devs saying that sharing agents would be released in "about two weeks". That was two months ago.
Mini rant over... But my point is that skills are just "agents + auto-selecting sub-agents via a short description" and we'll see this pattern everywhere soon. Claude Skills have some additional sandboxing but that's mostly only interesting for coders.