Freelance · AI Agent Engineer

Shivam Sharma
building the agent layer.

I design and ship agent-integrated software — invoicing systems that talk to assistants, callable agents, media delivery, booking, and personal automation. If your customer now lives inside Claude, Codex or Cursor, your product needs to live there too.

  • invoicing in agents
  • callable workflows
  • media delivery
  • booking automation
01

Current focus

agent-integrated software & callable workflows
02

Availability

accepting 2 briefs for Q3 · remote / async

30+ agent integrations

Selected Work

Three projects, three agents shipped.

Each block expands on scroll. Text on the left, the automation wire-graph on the right — the actual flow the agent runs.

openclaw is an agent that runs a full LinkedIn content loop without a human in the middle. You hand it a topic or a draft angle; it drafts, polishes to your voice, schedules, and publishes to LinkedIn — then watches reactions and feeds the signal back into the next draft.

The hard part wasn't the writing. It was the state machine: keeping drafts, schedules, published slugs and analytics coherent across runs, and failing gracefully when LinkedIn's API rate-limits mid-publish. openclaw treats the whole loop as one callable agent, not a queue of scripts. Live at linkedin.com/in/shivam-sharma

node · typescriptlinkedin APIstate machineself-hosted
automation · openclaw● live
agent stepdata flowfeedback loop

Newsletter CLI is the connective tissue between a developer, their coding assistant, and a technical brief that actually matters to them. You install it once; your assistant authenticates, reads your profile, and later fetches a brief tuned to your stack, tools and workflows.

The product is not a newsletter publisher — it's a trusted local setup layer. The emotional promise: your assistant knows what technical updates matter to you. Live at shivamsharma.shop/cli/

node · CLIOAuth 2.0 device flowverified API profilecodex · claude prompts
automation · newsletter-cli● live
agent stepdata flow

InvoiceShelf is a customized fork of the open-source invoicing platform, extended with a native CLI and a local MCP server. A user signs in through OAuth device authorization; Codex or Claude can then search, describe, read, and—when explicitly authorized—write invoices, estimates, customers, expenses, and payments for one selected company.

The hard part was the security boundary: discover server capabilities, request the smallest useful scope, rotate refresh tokens safely, and reuse a CLI profile without copying credentials into an assistant's config. The Laravel and Vue application remains the source of truth while the agent gets a compact, auditable interface. Explore the work on GitHub .

OAuth 2.0 device flowMCP · Codex · ClaudeLaravel · VueDocker
integration · invoiceshelf● live
agent stepdata flowfeedback loop
Manifesto

Agents are becoming the interface of the future — and I'll help you get visible there.

For thirty years the interface was a screen you stared at. The next interface is a sentence you say to an agent — and the agent goes and does the work behind it. Your customers will not open your website first; they will ask their assistant, and the assistant will pick whoever it can reach, call, book and remember.

If your product is not callable, readable and memorable by an agent, it becomes invisible by default. The brief I take on is simple: make your software a thing the agent already knows how to use — so when a human asks, your product is the answer the assistant reaches for.

— let's get you visible in the agent layer