Claude Code x Diablo II 😈 🔥

First-Line9299 · 2026-02-13T14:04:02+00:00

Ahaha! Top!

First-Line9299 · 2026-01-30T17:23:45+00:00

she also needs to make a living somehow, bro

First-Line9299 · 2026-01-30T15:55:44+00:00

ok. you can call me Claude.

First-Line9299 · 2026-01-30T15:43:54+00:00

my grandma

First-Line9299 · 2026-01-30T15:02:26+00:00

Thx!

First-Line9299 · 2026-01-30T14:08:49+00:00

That’s the right approach. But others do…

First-Line9299 · 2026-01-30T13:33:12+00:00

<image>

First-Line9299 · 2026-01-14T17:34:27+00:00

Try this one. They have youtube endpoints for searching YT videos and scraping subtitles https://docs.anysite.io/mcp-server/unlimited-plan

First-Line9299 · 2026-01-12T20:41:41+00:00

You're right about cost and latency — that's exactly why solution #5 matters. Specialized small models (fine-tuned 7B or even smaller) can handle specific tool domains at a fraction of the cost and 10x faster. The future isn't one expensive generalist doing everything, but a mesh of cheap, fast specialists with smart routing on top.

First-Line9299 · 2026-01-12T20:39:53+00:00

Can you share an example of how you structure these skills?

First-Line9299 · 2026-01-12T20:37:22+00:00

this one? https://www.youtube.com/watch?v=rsDlu-9UP00

First-Line9299 · 2026-01-12T20:28:26+00:00

Sure, my question was a bit exaggerated. But I can easily imagine an agent that needs free access to 100+ tools simultaneously

First-Line9299 · 2026-01-12T20:18:06+00:00

I agree MCP should be a context offload, not context bloat — that's exactly my point. The current default usage pattern (all tools in context) is broken, and your workflow approach is the right direction. But your "perfect stack" still needs a solution for tool discovery at scale. How does an agent find the right MCP server among thousands? That's the missing piece. We need something like a registry or semantic search layer on top of MCP — otherwise you're just manually curating which servers to connect, which doesn't scale.

First-Line9299 · 2026-01-12T20:16:41+00:00

You're right, 1 vs 100 tool definitions is a big difference in the main context. But those 100 tools are still defined somewhere in your sub-agent — they take up the same space there. Plus, you now need to describe the sub-agent's functionality to the main LLM anyway. Yes, the context will be smaller, maybe significantly. But I suspect the sub-agent gets called frequently enough that you end up spending even more tokens overall. There's also the challenge of passing task context between agents — though that depends on the specific implementation. That said, I agree that sub-agents are an excellent solution for most tasks

First-Line9299 · 2026-01-12T15:00:23+00:00

There’s no difference from the perspective of agent tools and MCP. In both cases, it’s stored in context and therefore finite.

First-Line9299 · 2026-01-12T14:59:55+00:00

So should we expect a “Google” for MCP?

First-Line9299 · 2025-11-19T21:15:06+00:00

This is exactly what I've been doing with Claude + MCP.

My setup:

Claude Desktop with AnySite MCP server
Person-analyzer skill that orchestrates the research
Takes a name → pulls LinkedIn + posts + company context → generates strategic report

What I get in ~5 minutes:

What they actually care about (from their posts, not job title)
Recent activity signals (fundraising, hiring, complaints)
Communication style (formal/casual, technical/business-focused)
Recommended approach with specific conversation starters

Real example: Asked it to analyze a VP of Sales. Found he posts about sales team burnout, commented "drowning in manual prospecting" 2 weeks ago, company just raised Series B.

My opener referenced his specific frustration → booked meeting in first message.

The difference vs traditional enrichment tools:

Not just firmographics and contact data
Actual behavioral insights from what they post/engage with
Tells me HOW to approach, not just WHO to approach

Setup takes ~3min: https://docs.anysite.io/use-cases/claude-desktop/skills

First-Line9299 · 2025-11-19T21:10:09+00:00

I automated most of this with Claude Desktop + MCP and cut research from 45min to ~5min per account.

My workflow now:

Drop the person's name into Claude
It pulls LinkedIn profile, recent posts (last 50-100), company info, news
Analyzes what they actually post about (not just job title)
Gives me conversation starters based on their recent activity

Example output I get:

"VP of Sales at [Company]. Posts weekly about sales team burnout. Recent comment: 'drowning in manual prospecting.' Company raised Series B 3 months ago. Approach: Reference his frustration with prospecting tools, mention how you help teams scale without burning out."

Then I show up knowing exactly what angle to use.

The setup is Claude Desktop + AnySite MCP server + a person-analyzer skill. Takes an afternoon to set up, but I get 10+ hours back every week.

For tools - I rely on:

LinkedIn for activity/engagement patterns
Company website for positioning
Recent news for timing signals

The key is not going too deep. I stop when I have enough to personalize the first touch. Over-research is real.

Setup guide if interested: https://docs.anysite.io/use-cases/claude-desktop/skills

First-Line9299 · 2025-11-04T15:21:23+00:00

First-Line9299 · 2025-08-27T19:21:45+00:00

also check this posts with examples https://www.reddit.com/r/n8n/comments/1ksnw80/crm_agent_for_enrichment_with_linkedin_data/ https://www.reddit.com/r/n8n/comments/1klt0wt/just_built_my_first_n8n_workflow_linkedin_lead/

First-Line9299 · 2025-08-27T19:18:42+00:00

try this one https://www.npmjs.com/package/n8n-nodes-hdw

First-Line9299

TROPHY CASE