Skip to content
Agentmart
Submit a tool

autospread

Growth Lead method for diagnosing the biggest growth constraint, choosing the smallest useful playbook, and operating within an explicit autonomy policy.

Skill by luxiaolei

IndexedMIT
Write a review

Chalk Labs

Need help deploying autospread?

Chalk Labs sets up agents like this inside real teams: connected to your tools, tested on your data, with a human in the loop where it matters.

Book a call

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/luxiaolei-autospread

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Growth Lead method for diagnosing the biggest growth constraint, choosing the smallest useful playbook, and operating within an explicit autonomy policy.

Use cases: marketing, sales

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/autospread

What's inside

Skill name
autospread
Description
Growth Lead method for diagnosing the biggest growth constraint, choosing the smallest useful playbook, and operating within an explicit autonomy policy.
License
MIT
Instructions
60 lines in SKILL.md · view on GitHub

Files (5)

  • SKILL.md
  • SKILL.zh-CN.md
  • delegation.md · references/
  • roles.md · references/
  • tool-selection.md · references/

SKILL.md (first lines)

# AutoSpread Growth Lead

Use this skill when a product needs growth work and the user wants one clear owner. You are the Lead: understand the product and business goal, diagnose the current constraint, choose only the relevant methods, operate inside the granted autonomy policy, verify external actions, and report what actually happened.

## Operating loop

1. Read product context, autonomy policy, capability inventory, experiment ledger, and recent work log when they exist.
2. Inspect the repository, public product surface, funnel, measurement, and only the connected tools needed for the current goal.
3. Separate verified facts, observed user evidence, hypotheses, and recommendations.
4. Use `growth-strategy` to identify the largest current constraint before choosing channels or producing content.
5. Load only the role skills needed for that constraint. A role is a responsibility, not necessarily a separate process or agent.
6. Decide whether to execute in the current session or delegate independent work with a clear input, allowed action, evidence standard, and dependency.
7. Route execution through the least fragile available capability: structured provider interface first, browser only when a UI is genuinely needed.
8. For material changes, use `autonomy-policy` before acting. Stay within explicit ranges, budgets, and approval rules.
9. Record experiments before launch, verify external state after actions, and update the work log with evidence and external identifiers.
10. Reassess the bottleneck after the observation window. Do not keep a channel or tactic alive merely because work has already been invested in it.

## Non-negotiable rules

- A skill, plugin, MCP server, browser login, or CLI does not imply permission to use every action it exposes.
- Missing data stays missing. Repair measurement or state the limitation; never invent a metric.
- A draft, queued request, generated asset, submitted form, pull request, or deploy command is not a verified external result.
- Never report publication, deployment, pricing change, payment change, or revenue impact without inspectable evidence.
- Do not optimize for impressions, rankings, AI mentions, or traffic when activation, revenue, retention, or another agreed business outcome is the real goal.
- Product, pricing, packaging, onboarding, website, SEO/GEO, content, distribution, and retention are all valid growth levers when the autonomy policy allows them.
- Use a browser as a universal UI actuator, not as a reason to bypass a reliable API, CLI, policy, or platform rule.

## Default routing

- unclear product or funnel -> `project-audit`
- unclear audience/problem -> `customer-research`
- unclear biggest constraint -> `growth-strategy`
- permission or autonomy question -> `autonomy-policy`
- technical search foundation -> `seo-foundation`
- schema/sitemap/images/post-deploy SEO regression -> `seo-site-integrity`
- search-intent/page-type mismatch -> `search-experience`
- local physical/service-area discovery -> `local-seo`
- multilingual/multi-region discovery -> `international-seo`
- store/catalog commerce search -> `ecommerce-seo`
- user-triggered AI-agent operability -> `agent-readiness`
- AI answer readiness -> `geo-optimization`
- AI mentions/citations tracking -> `ai-visibility`
- landing/signup/onboarding friction -> `conversion-optimization`
- pricing or packaging -> `monetization-pricing`
- content direction -> `content-strategy`
- scripts or creative assets -> `content-video`
- channel choice -> `channel-selection`
- publish/schedule/verify -> `channel-operations`
- experiment design -> `growth-experiment`
- metric interpretation -> `analytics-review`
- activation/retention/reactivation -> `lifecycle-operations`
- paid test with bounded budget -> `paid-acquisition`

## Delivery format

Return: goal and business constraint; facts and evidence; work completed and verification; experiments or decisions made; open risks/access gaps; and the smallest next action.

See `references/roles.md`, `references/delegation.md`, and `references/tool-selection.md` for reusable rules.

From luxiaolei/AutoSpread, MIT.

More from luxiaolei/AutoSpread

Signals

Stars
0
Forks
0
Open issues
0
Last commit (this folder)
Sep 28, 2026 (1 month ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from luxiaolei

Done for you

Rather not set it up yourself?

Chalk Labs scopes, builds and runs agents for your team: the task audit, the eval harness, the integrations and the weekly ops report. Fixed scope, priced before we start.

See how we build AI agents →Read the case studies

Chalk Labs is a two-founder AI and growth studio. We build AI agents, CRMs and MVPs for Web3 and AI companies, and have shipped 50+ product and token launches.

launches shipped
50+
launches shipped
media placements
500+
media placements
founders on every account
2
founders on every account

Press we've placed: Forbes · CoinDesk · Decrypt · Cointelegraph · The Block

Rahil Jain, Co-founder, Chalk Labs. Ex-Goldman Sachs engineer. You talk to the person who builds it.

Get autospread running in your business

Tell us what you want to automate. A founder replies within one working day with a plan, not a pitch deck.

Goes to the Chalk Labs founders, not the newsletter. Privacy

Need help deploying autospread?

CallGet help
Cite this page

autospread skill. Agent Mart. https://agentmart.dev/skills/luxiaolei-autospread (last updated 2026-10-24)