skruban.com
success
Claude Code
intent

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

22steps
89.5sduration
$1.1559cost
363,820tokens
26 steps4 reasoning steps9 searches
home
docs
home
home
search
search
/projects/finance
/essays/fpl-optimisation
docs
/projects
search
/books
search
/essays
/curriculum
search
search
/sk-ruban
/in/skruban
search
search
search
46%
on-site discovery
77%
reliability
23%
link following
path origin
  • previous resource23%
  • web search54%
  • prior knowledge23%
insight

The agent assembled a comprehensive understanding of skruban.com by combining web search, direct site navigation, and cross-reference with external profiles (GitHub, LinkedIn, Goodreads). The site itself is minimally descriptive—a personal portfolio with no explicit mission statement—so the agent had to synthesize information from multiple fetches and external sources to answer the task. Most content pages returned truncated HTML, preventing full inspection of body text, but the agent successfully inferred the site's purpose, audience, and lack of pricing model from navigation structure, metadata, and external validation.

  • ›The homepage and content pages use HTML compression that prevented the agent from viewing full body text; all responses were truncated at ~4400 chars. The agent relied on page titles, metadata descriptions, and URL structure rather than rendered content to understand each section.
  • ›The site has no dedicated pricing page (404 on /pricing) and no commercial product offering—this is a personal portfolio. The agent correctly identified this by the absence of pricing infrastructure and by corroborating with external sources (GitHub, LinkedIn, Goodreads profiles).
  • ›Navigation structure and section titles (Essays, Projects, Books, Curriculum, Links) were discoverable via site search results and direct URL guessing, but the site does not publish a sitemap or explicit navigation menu in the fetched HTML. The agent had to use web search to enumerate all available sections.
  • ›External references were critical to answering 'who it's for' and background context: GitHub profile revealed technical work, LinkedIn showed role as 'Rates Quant Intern', Goodreads showed 1,475 books. The site itself does not link to or embed this information.
  • ›The agent could not fetch actual essay content or project details—only metadata and page structure. Specific project examples (e.g., 'FPL Optimisation with Julia & JuMP') came from page titles and metadata descriptions, not from body text.

See every agent that visits skruban.com

Front builds the agent version of your site and shows which agents visit, what they came for, and what your pages couldn't answer.

or talk to us about agent readiness →