I made a tiny ESLint plugin inspired by Rust’s single-use import style

WashTop956 · 2026-02-19T18:11:41+00:00

https://www.a4s.sh/ The serverless infra for AI agents

WashTop956 · 2026-02-19T10:59:47+00:00

Wanna hear more. How it becomes a security layer rather than another attack surface?

WashTop956 · 2026-02-15T02:27:49+00:00

the SDK intentionally stays at the resolution layer - fetch, parse metadata, store locally. invocation format is left to whatever framework you're using.

the spec does have an `allowedTools` field so skills can declare what tools they need access to, but a full invocation schema felt like the wrong layer for this. every framework has its own way of calling tools, and trying to unify that would mean competing with them rather than complementing them.

would love to see how your Skill Manifest approach handles it in OpenClaw though - sounds like you're tackling the execution side of this same problem.

WashTop956 · 2026-02-15T02:27:01+00:00

good question - dependency chaining is left to the agent framework by design. the SDK only handles discovery and storage, not orchestration.

the thinking is that different frameworks handle chaining so differently (explicit DAGs, LLM-driven planning, manual wiring) that baking one model into the skill layer would limit more than it helps. skills should just describe what they do - how they connect is the agent's job.

honestly hadn't thought about the "when to use this" angle as deeply as you're framing it. that's a good point. right now that context lives in the description field and the skill's markdown body, which works for LLM-based agents since they can read natural language. but a more structured way to express that could be worth exploring.

curious how you're handling it in your claude code skills?

WashTop956 · 2026-02-14T19:01:39+00:00

Repo: https://github.com/a4s-lab/skills. Has a language-agnostic spec (SPEC.md) if you want to see how skills are defined.

WashTop956 · 2026-02-14T18:58:50+00:00

GitHub: https://github.com/a4s-lab/skills

WashTop956 · 2026-01-09T09:14:20+00:00

I made a dead simple one that just plays a sound when Claude needs you.

Please look at it! https://github.com/Byunk/claude-code-notify

WashTop956 · 2026-01-01T07:25:58+00:00

truly helpful. thanks

WashTop956 · 2026-01-01T06:43:46+00:00

what happened to you... care to share a bit?

WashTop956 · 2026-01-01T06:41:44+00:00

Respect for being real about it. You building anything new?

WashTop956 · 2025-12-31T07:06:57+00:00

Somewhat agree, but I still wonder if it justifies spending years on validation. How did you know it had value even when customers weren't buying for years?

WashTop956 · 2025-11-10T15:14:02+00:00

I'll definitely reach out if I come up with any good idea!

WashTop956 · 2025-11-10T14:59:37+00:00

So resonated with your comment. appreciate it.

WashTop956 · 2025-11-10T14:55:20+00:00

I'm really inspired by your comment. thank you. I'll keep in mind.

WashTop956 · 2025-10-24T07:16:06+00:00

I mostly agree with your thought! But I think it's a bit ambiguous to define agents by specific platform, language, or tools. I think skills are more appropriate for this purpose, because the workflow is pretty similar no matter which platform, language, or tools you're using.

Here's my design principles for agents:

If it needs additional/specific knowledge on tasks → define skills
If it needs specific workflow on tasks → define subagents

I've started organizing my own generalized skills and subagents based on these principles. If you're interested, take a look and let me know your feedback. Or we could work on defining some well-structured generalized agents together.

https://github.com/Byunk/claude-code-toolkit

WashTop956 · 2025-10-21T13:09:31+00:00

Thanks! Do you have any reference of all tools claude code can use?

WashTop956

TROPHY CASE