Scorpio ♏️

Bullish

[LΞKS @leks_onchain]

Maybe I never really doxxed myself on here 😂

So, here’s the face behind the tweets.

Apart from Web3, I also own a fashion brand where I make and design men’s outfits

I’m also a final year student at the University of Ilorin.

Still learning, building and figuring things out one step at a time.

I’ll be sharing some of my work here too, so you get to see that side of me.

Looking to connect with more people on this space.

If you see this, tap in. Let’s connect 🤝

[Scorpio ♏️ @ajiiide]

@rokha_agent @GoblinBuilds 💣💣💣

[Scorpio ♏️ @ajiiide]

I find the composability side of agents pretty interesting.

Instead of putting every capability into one system, builders can combine different skills to handle specific parts of a workflow. That makes it easier to build flexible agent systems.

@rokha_agent @GoblinBuilds $ROKHA

[Scorpio ♏️ @ajiiide]

The more I explore Rokha, the more its layers stand out.

Skills give agents capabilities, MCP connects tools, the runtime handles execution, and traces make the process easier to follow.

That’s what makes @rokha_agent interesting. @GoblinBuilds $ROKHA

[Scorpio ♏️ @ajiiide]

@rokha_agent @GoblinBuilds $ROKHA

[Scorpio ♏️ @ajiiide]

@rokha_agent @GoblinBuilds Insane project

[Scorpio ♏️ @ajiiide]

The parts of agent infrastructure that work quietly in the background are often the most important.

Sandboxes, permissions, tool connections, and traces may not be flashy, but they give agents the structure needed to execute real tasks.

@rokha_agent @GoblinBuilds $ROKHA

[Scorpio ♏️ @ajiiide]

@rokha_agent @GoblinBuilds Amazing project

[Scorpio ♏️ @ajiiide]

A2A gets interesting when agents can specialize.

An agent doesn’t need to know everything itself if it can connect with another agent that has the capability needed for a specific task.

That could make agent workflows more flexible. @rokha_agent @GoblinBuilds $ROKHA

[Scorpio ♏️ @ajiiide]

Nice work

[Scorpio ♏️ @ajiiide]

The more I explore Rokha, the more its layers stand out.

Skills give agents capabilities, MCP connects tools, the runtime handles execution, and traces make the process easier to follow.

That’s what makes @rokha_agent interesting. @GoblinBuilds $ROKHA

[Scorpio ♏️ @ajiiide]

The parts of agent infrastructure that work quietly in the background are often the most important.

Sandboxes, permissions, tool connections, and traces may not be flashy, but they give agents the structure needed to execute real tasks.

@rokha_agent @GoblinBuilds $ROKHA

[Scorpio ♏️ @ajiiide]

MCP gives agents a way to connect with tools without needing every capability inside one environment.

That flexibility becomes more useful as agents start working across larger and more complex workflows.

@rokha_agent @GoblinBuilds $ROKHA

[Scorpio ♏️ @ajiiide]

A2A gets interesting when agents can specialize.

An agent doesn’t need to know everything itself if it can connect with another agent that has the capability needed for a specific task.

That could make agent workflows more flexible. @rokha_agent @GoblinBuilds $ROKHA

[Scorpio ♏️ @ajiiide]

I find the composability side of agents pretty interesting.

Instead of putting every capability into one system, builders can combine different skills to handle specific parts of a workflow. That makes it easier to build flexible agent systems.

@rokha_agent @GoblinBuilds $ROKHA

[Scorpio ♏️ @ajiiide]

@GoblinBuilds Nice work rate 🔥

[Scorpio ♏️ @ajiiide]

@GoblinBuilds Keep up the work

[Scorpio ♏️ @ajiiide]

@striverfbea @rokha_agent @GoblinBuilds 🔥🔥🔥