One-command skill install from docs URL
Teach users to install the product's skill straight from the docs URL with one command so discovery turns into first use while intent is still warm.
Why this can grow a startup
A machine-readable surface is still incomplete if the user has to reverse-engineer how to activate it. One install command collapses the gap between reading the docs and using the capability inside an assistant workflow. That matters most for technical buyers because they often decide whether a tool feels real in the first minute, not after a long setup detour.
Source-backed example
Mintlify shows users how to run `npx skills add https://your-docs-domain.com` so agents can load the site's skills into context manually.
Source-reported evidence
Source: Mintlify Docs · Browse Mintlify Docs tactics
Mintlify documents a single `npx skills add https://your-docs-domain.com` command for manual skill installation
Attributed to the cited source; GrowthDex has not independently verified it. Use this as context, not as a forecast, benchmark, or recommended target.
Evidence scope: claims and metrics are attributed to the linked source; GrowthDex has not independently replicated the reported result. Check the original context and validate fit before applying it. Read the evidence methodology.
Source discovered: May 28, 2026
When to use it
Use this when AI Search, Documentation, Activation is relevant to agent enablement, activation, self-serve onboarding and you can run a bounded test with a free budget.
When not to use it
Do not use it as a substitute for customer evidence, a clear owner, or a measurable stop condition. Local platform rules and market behavior still need checking.
How to do it
- Choose one target segment and define the exact next action this tactic should prompt.
- Adapt the tactic to AI Search and Documentation, using evidence from Mintlify Docs as context—not as a promised result.
- Record a baseline for: Share of target users completing the product's first-value action. Set a guardrail that would make you pause the test.
- Run a narrow pilot and choose a test window that fits the normal decision or use cycle; do not scale before you have observed the full cycle.
- Compare the signal with its baseline. Scale only if the intended action improves without crossing the guardrail; otherwise revise one variable or stop and record what you learned.
Compare a stack for your situation
Compare source-backed tactics against your product, stage, budget and channel strengths, then choose one experiment to test.
Explore the context
Did you launch this experiment?
Report a launch to help us understand which growth ideas founders put into practice.
Apply this with an operator
Choose product surfaces that compound distribution without hiding weak activation or retention.
SOURCE HUB
More tactics from Mintlify Docs
Explore related GrowthDex examples and evidence connected to Mintlify Docs.
Open Mintlify Docs source hub