--- title: I'm the agent for Claude now | daily.dev description: An Aha! engineer describes how they restructured their support rotation workflow by building a custom Claude skill with five production debugging tools: a log... canonical: https://daily.dev/posts/i-m-the-agent-for-claude-now-gjjj8wf41 twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: I'm the agent for Claude now | daily.dev og:description: An Aha! engineer describes how they restructured their support rotation workflow by building a custom Claude skill with five production debugging tools: a log... og:url: https://daily.dev/posts/i-m-the-agent-for-claude-now-gjjj8wf41 og:image: https://api.daily.dev/og/posts/gjjJ8WF41.png og:image:alt: I'm the agent for Claude now og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # I'm the agent for Claude now **[RUBYLAND](https://daily.dev/sources/rubyla)** · 4 min read · 0 upvotes · 0 comments ## Summary An Aha! engineer describes how they restructured their support rotation workflow by building a custom Claude skill with five production debugging tools: a log link generator, config explorer, query analyzer, record history viewer, and a Rails console script generator. Instead of manually navigating log viewers and writing ad-hoc scripts, Claude now directs the engineer to gather specific data and generates safe, consistent production scripts. The result is an inverted workflow where the engineer acts as Claude's agent — fetching data on demand — rather than doing the investigative work themselves. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### How can I use Claude to help with production debugging without exposing customer data? Pull only pieces of a support ticket, generalize the details, and describe the situation to Claude rather than pasting raw customer data. One team built a custom skill with five tools: a log link generator, config explorer, query analyzer, record history viewer, and a script generator for production console access that avoids raw customer content, only surfacing metadata like IDs, timestamps, and counts. _daily.dev surfaces engineering write-ups on safely wiring AI agents into production debugging workflows._ ### What is a good pattern for generating safe Rails production console scripts with an AI assistant? Have the assistant always write scripts that set the current account and user explicitly, focus only on metadata such as IDs, timestamps, and counts rather than raw customer content columns, and end with a single clean puts statement so the output isn't mixed with Rails log noise. This replaced inconsistent, improvised scripts that sometimes leaked customer data or buried results in stdout. _Teams standardizing safe production scripting patterns follow this kind of practical AI workflow writeup on daily.dev._ ## Similar posts on daily.dev - [Claude Skills](https://daily.dev/posts/claude-skills-cc0t7hjf8) · RUBYLAND · 1 upvotes · 0 comments --- Tags: [#ai-coding](https://daily.dev/tags/ai-coding), [#claude](https://daily.dev/tags/claude) [View this post on daily.dev](https://daily.dev/posts/i-m-the-agent-for-claude-now-gjjj8wf41) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"I'm the agent for Claude now","url":"https://daily.dev/posts/i-m-the-agent-for-claude-now-gjjj8wf41","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/i-m-the-agent-for-claude-now-gjjj8wf41"},"datePublished":"2026-06-22T19:57:08.406Z","dateModified":"2026-09-13T21:14:37.763Z","description":"An Aha! engineer describes how they restructured their support rotation workflow by building a custom Claude skill with five production debugging tools: a log...","image":"https://media.daily.dev/image/upload/s--qPvKM23u--/f_auto/v1722860399/public/Placeholder%2009","thumbnailUrl":"https://media.daily.dev/image/upload/s--qPvKM23u--/f_auto/v1722860399/public/Placeholder%2009","isAccessibleForFree":true,"articleSection":"RUBYLAND","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"RUBYLAND","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/rubyla","url":"https://daily.dev/sources/rubyla"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/i-m-the-agent-for-claude-now-gjjj8wf41","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"ai-coding,claude","timeRequired":"PT4M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"RUBYLAND","item":"https://daily.dev/sources/rubyla"},{"@type":"ListItem","position":3,"name":"I'm the agent for Claude now"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/i-m-the-agent-for-claude-now-gjjj8wf41#faq","mainEntity":[{"@type":"Question","name":"How can I use Claude to help with production debugging without exposing customer data?","acceptedAnswer":{"@type":"Answer","text":"Pull only pieces of a support ticket, generalize the details, and describe the situation to Claude rather than pasting raw customer data. One team built a custom skill with five tools: a log link generator, config explorer, query analyzer, record history viewer, and a script generator for production console access that avoids raw customer content, only surfacing metadata like IDs, timestamps, and counts. daily.dev surfaces engineering write-ups on safely wiring AI agents into production debugging workflows."}},{"@type":"Question","name":"What is a good pattern for generating safe Rails production console scripts with an AI assistant?","acceptedAnswer":{"@type":"Answer","text":"Have the assistant always write scripts that set the current account and user explicitly, focus only on metadata such as IDs, timestamps, and counts rather than raw customer content columns, and end with a single clean puts statement so the output isn't mixed with Rails log noise. This replaced inconsistent, improvised scripts that sometimes leaked customer data or buried results in stdout. Teams standardizing safe production scripting patterns follow this kind of practical AI workflow writeup on daily.dev."}}]} ```