Growth idea action plan
Reverse-proxy forwarding for agent skill paths
If docs sit behind a proxy or custom domain, forward `/skill.md`, `/.well-known/skills/*`, and `/.well-known/agent-skills/*` instead of letting the discovery layer die at the edge.
Why this can grow a startup
A capability file only helps if the agent can actually fetch it. Reverse proxies often preserve the pretty docs URL while quietly dropping newer AI-discovery paths. Forwarding the skill routes keeps the capability layer reachable, which matters because agents often start at the public hostname, not the upstream docs subdomain where the files were first generated.
Ian's take
From scaling consumer platforms across MENA and Southeast Asia, my default is to distrust growth work that only looks good in a slide. For SEO and AI search, I care less about clever keyword tricks and more about clarity. A buyer, crawler, or answer engine should quickly understand who this is for, why it works, what proof backs it, and what page deserves to be cited. I would run it small enough to learn quickly, then only scale the parts that real users repeat, save, reply to, or buy from. For this tactic, I would watch one clear growth signal before putting more time or budget behind it.
Action plan
- Define one narrow startup segment where reverse-proxy forwarding for agent skill paths can create a measurable lift.
- Turn the tactic into one offer, page, campaign, or workflow for the AI Search and Website channel.
- Use the evidence from mintlify.com to set the first version of the message, format, and audience.
- Launch a small test for 7 to 14 days with one success metric: one measurable growth signal.
- Review the result, keep the winning message, remove weak variants, and turn the learning into a repeatable growth playbook.
Source-backed example
Mintlify tells teams using a reverse proxy to forward `/skill.md`, `/.well-known/skills/*`, and `/.well-known/agent-skills/*` to the Mintlify subdomain so agents can still discover the files.
Source: Mintlify Docs (mintlify.com)
GrowthDex source hub: Mintlify Docs
Last checked: 2026-05-27
Adjacent tactics in the same lane
If this page is close to your problem, these tactic pages usually belong in the same working set.
- Root skill.md for product capability discovery same source · 3 shared channels · 1 shared stage
- Well-known llms aliases for agent compatibility same source · 2 shared channels · 2 shared stages
- llms discovery headers on every page same source · 2 shared channels · 2 shared stages
- Skill frontmatter with compatibility and tool constraints same source · 2 shared channels · 2 shared stages
Related GrowthDex essays
- An agent needs a capability page, not just a crawl map AI Search, brand trust, technical SEO
Read GrowthDex essays
The Blog turns real growth tactics into plain-English case studies by niche, channel, and buying situation.
Why this is worth your time
GrowthDex starts with tactics that founders, marketers, and product teams have actually tried. Each essay turns the evidence into a practical move you can test without pretending one case study is a guarantee.
Ian Goh has helped grow consumer platforms across Southeast Asia, India, and MENA. His work includes scaling Tiki to 100M+ users, doubling BIGO's MENA revenue in 7 months, and increasing OYO's direct booking share across 6 Southeast Asian markets.
- Helped scale Tiki to 100M+ users.
- Doubled BIGO's MENA revenue in 7 months.
- Raised OYO's direct booking share by 50% across 6 Southeast Asian markets.
Want help turning this into a growth system?
If you want someone to pressure-test this against your real market, Ian works with founders on growth, market entry, and operator-led distribution.
Work with Ian on growth advisory