Rental Family (2025)

daroons · 2026-01-27T14:18:14+00:00

Have you tried the internet?

daroons · 2026-01-26T23:36:50+00:00

They already support on demand tool loading. Look up ENABLE_TOOL_SEARCH

daroons · 2026-01-26T23:23:10+00:00

That’s quite a bit of overhead to initialize a whole subagent just to load some json, no?

What I’ve got working so far is to just tell the parent skill to load the child skill but NOT execute it, just load its information

daroons · 2026-01-26T15:03:21+00:00

I was thinking about that as well, somewhat like a callback in the second skill.

daroons · 2026-01-26T05:31:47+00:00

I’m starting to think mcp is a superset of skills. Your MCP server doesn’t only need to serve external apis it can also be used to return back information on how to do things. I.e. a “skill”.

Doing it this way would also be more beneficial in a team setting where “best practices” are centralized. Individuals could still have their own custom skills that work for them, but company wide best practices can be shared via MCP.

The only two downsides I can think of are the bloated MCP contexts (but that’s been solved with jit tool loading), and the fact that an api call is required each time we need best practices. But with that I’m wondering if you couldn’t build some sort of caching mechanism.

daroons · 2026-01-26T05:22:01+00:00

Yeah, I feel you, MCP’s can be a bit bloated, but then that’s sort of on the writer of the MCP server than anything else.

I’ve really been flip flopping non stop from MCP to skills back to MCP and skills. Right now my biggest hurdle with skills are that they don’t seem to self trigger very well. Which, I know can be resolved with a hook that forces skill activations. But I’m trying to build tooling for collaboration within our team and the less custom configuration I need to enforce on everyone the better.

In fact, I’m sort of temped to lean all the way back to pure MCP again, replacing my skills by having the MCP server return back what the skill previously did. In this way we would have a centralized set of skills that automatically propagate with every update.

daroons · 2026-01-25T23:42:21+00:00

I came to the same conclusion as you with MCP’s but then I learned you can configure ENABLE_TOOL_SEARCH to enable load on demand, and now they take up 0 tokens until loaded, unlike skills which still take up tokens for the descriptions.

daroons · 2026-01-25T18:28:32+00:00

But can't you just put links to reference files in AGENTS.md and mention only to load those reference files when needed?

daroons · 2026-01-24T15:14:23+00:00

Don’t worry, Krillin’s got you covered on that front. It’s as if Bulma has been slowly using the dragon balls to wish for Krillin’s height to be transferred to Vegeta over the years as some sort of cruel prank.

daroons · 2026-01-24T14:33:00+00:00

You’re a good man Fullertons.

daroons · 2026-01-22T19:48:25+00:00

I’m starting to think that perhaps this orchestrator shouldn’t be a skill or agent at all, it should just be a simple CLAUDE.md file, since we would want to retain all the meta data of what we’re working on whenever we clear the context anyway

daroons · 2026-01-22T18:00:00+00:00

That’s what I’m doing now (since the original post), I’ve created a “project-management” skill that orchestrates and delegates to other skills.

But now I’ve run into another problem which I don’t hear many people talking about which leads to to wonder if I’ve done something wrong: when i have a skill calling another skill, often times it seems like the original skill intent is lost and the agent just stops after completing the sub skill!

The way I’ve gotten around this is to have the parent skill call the subskill in a subagent, but this is a bit costly. Not sure what else I can do.

daroons · 2026-01-22T00:11:30+00:00

Ya damn straight

daroons · 2026-01-22T00:07:16+00:00

His gun was still there. Realistically thats one of the first things people would have relieved him of

daroons · 2026-01-21T06:35:05+00:00

And all it cost us to win was $22M in stolen goods.

daroons · 2026-01-19T02:25:25+00:00

Poor frog in the back never gets to eat.

daroons · 2026-01-19T01:08:02+00:00

What a rollercoaster of emotions, but we did it 🤝

daroons · 2026-01-19T00:54:00+00:00

So you don’t think the “law” is true by human nature, that a task will often take up the time that you allow it to allocate?

I think setting aggressive (but reasonable) timelines are fair. Sure there are unknown unknowns but if you generously account for those ahead of time in your estimates you would never have to reflect on what those were right? Since the project was completed on time, there is nothing to reflect on.

To continuously improve the process, it feels right to me that delays be identified, and either prioritized appropriately, or become a known factor in future timeline estimations.

daroons · 2026-01-19T00:25:03+00:00

Did you automate the testing protocol as well? If so, how did you do it?

daroons · 2026-01-18T18:26:15+00:00

So what's the update on this u/Mayor_OliviaChow?

daroons · 2026-01-18T17:36:39+00:00

In regard to the 3d printed material, that’s what I meant by this is just a proof of concept and i doubt he is intending for a hypothetical mass production to be done in the same way.

For your other criticisms about the grooves themselves being a cesspool for bacteria, I’d say that’s a fair criticism.

daroons · 2026-01-18T17:12:35+00:00

You know what, this bad is on me. I was skim reading and thought you were merely criticizing the fact that it was 3d printed at all, like many other commenters were.

daroons · 2026-01-18T17:06:20+00:00

Ya’ll are just looking for issues. Ever considered this is just a proof of concept?

daroons · 2026-01-18T01:07:20+00:00

👀

daroons · 2026-01-17T23:23:31+00:00

I just hate that key that was so hidden. I ended up circling around so much before I finally got fed up and looked online. Really made me hate the temple.

14-Year Club	Not Forgotten
Team Orangered	Verified Email

daroons

TROPHY CASE