@macebake

predatory infovore, computer person, friend to LLMs, @tessl_io

 London
macey.info
Joined April 2012
  • Tweets726
  • Following385
  • Followers366
135Media
My main takeaway is that skills are software, and the same rules apply. The things that make a bad skill also make a bad software component, eg. being badly scoped. "Should we factor this out" has become "Should we make a skill for this". Same stuff, different form factor
Thariq
@trq212Mar 17

Lessons from Building Claude Code: How We Use Skills

Article · @trq212
2
5
5
1,178
Ragebait immunity is an underrated media literacy skill.
73
Macey Baker retweeted
Liran Tal
@liran_talApr 8
if you find yourself creating skills a lot, you might want to check out my skills-creator-extra on the @tessl_io registry
1
6
1
16
1,995
Me when I hit the rate limits on my Codex microwave
Tibo
@thsottiauxApr 1
Announcing Codex. A new product from OpenAI that moves beyond coding, into cooking. We were already cooking before, but now *you* can cook too ... with Codex. It is powered by the same technology as our other Codex products. You can just cook things.
2
169
Macey Baker retweeted
ashish@ashishgpt2Feb 6
no man talks to the same llm twice, for he is not the same man and it is not the same llm
29
364
23
3,731
99,327
Did you know that you can call agent skills *from* other agent skills? 😵‍💫 I wrote about this & other fun things you can do with skills here: tessl.io/blog/getting-creati…

Getting creative with agent skills

Tessl helps teams build AI-native software by giving coding agents structured, versioned context. Ship AI-powered systems that hold up in real codebases.

tessl.io
1
98
Ok but *what* did the lymph knowed
91
1
2
137
When exactly did we stop saying "screen name"
110
4
206
Amazing how much we take air travel for granted.
4
205
Please teach LLM-backed tools about themselves. This is bare minimum now. I should be able to debug your tool *with* your tool most of the time
124
There’s a pattern with LLM dev tools: First few tries? Magic. Then you hit the edges: the LLM guesses, hallucinates, ignores your tools, blows through tokens… and the magic fades fast. @macebake shares what she learned building an MCP server for a CLI tool. MCPs shine when the user already knows what’s possible. But for new users? The limits show up quick. Check out the article for pitfalls + practical tips 👇 ainativedev.co/6yl #AINativeDev #ClaudeCode #MCP
1
1
137
I wrote about some lessons learned building an MCP server... I imagine this will feel silly, for one reason or another, in a year's time. ainativedev.io/news/teaching…
3
5
457
On priming, a quick and dirty experiment with a `help` tool:
114
Just found out the sun has no proper scientific name. Wtf man
1
107
1
2
122
Petition to rebrand “playing the devil’s advocate” to “buying the dip”
112
MCP servers are amazing when the use case for a tool is obvious. Getting LLMs to discover and use tools for unique use cases, or new products / paradigms, is a different game.
135
I think about this often. The internet is a “third space” for a lot of people imo
Macey Baker@macebake11 Jan 2023
Do you think of the internet as more of a medium, or a place?
31%Medium
69%Place
0%Both (this is a cop out)
13 votes • Final results
1
2
178
Load more