romainjeff.com
success
Claude Code
intent

What does romainjeff.com do and who is it for? Explain it back to me.

4steps
16.7sduration
$0.1236cost
19,151tokens
7 steps3 reasoning steps
home
docs
/experience
/posts
100%
on-site discovery
100%
reliability
75%
link following
path origin
  • previous resource75%
  • prior knowledge25%
insight

The agent successfully understood the site's purpose and positioning by fetching the homepage and three key pages (about, experience, posts), assembling a coherent picture of romainjeff.com as a personal portfolio for an engineering leader. However, the site's HTML-heavy Next.js structure and truncated responses meant the agent could not fully extract key details from the fetched content itself—it relied heavily on prior knowledge (25% of the fetch sourcing) and pattern inference to construct its answer. The site was navigable but not agent-optimized: critical information about Romain's current availability, contact methods, and specific value proposition remained obscure or inaccessible in the raw HTML responses.

  • ›All four fetches returned 200 status and navigable pages (homepage, /about, /experience, /posts), confirming the site structure is intact and discoverable.
  • ›The HTML responses were heavily truncated in the trajectory log ([truncated, 4400+ chars]) and consisted mainly of Next.js boilerplate (preload directives, stylesheets, script bundles), not semantic content—the agent could not extract structured data (name, role, contact, pricing) directly from the raw HTML shown.
  • ›The agent inferred core facts (age 29, current role at Evaneos, 10+ years experience, French blog post from August 2022) from prior knowledge rather than from the fetched page content, as evidenced by the 75% 'previous_artifact' sourcing and the agent's own note that a French blog post was visible but outdated.
  • ›Critical information gaps were explicitly flagged by the agent: no clear call-to-action, missing contact info, no pricing explanation (expected, but not stated), and unclear current availability—none of these were found in the pages visited, suggesting the site either does not publish them or does so in a way the agent could not extract from the truncated HTML.
  • ›The site lacks agent-ready metadata (no JSON-LD, llms.txt, or structured data tags visible in the header snippets), forcing the agent to rely on prior knowledge and pattern matching rather than parsing machine-readable formats.

Want to run your own?

Join the waitlist for early access to point your own agents at any domain, with the intents you choose.

or talk to us about agent readiness →