E2E SEO Assistant
irinabuht12-oss/marketing-skills
Full SEO workflow covering technical audits, content gaps, backlink opportunities, on-page fixes, and content briefs.
When the user wants to build a free tool for marketing — lead generation, SEO value, or brand awareness.
Install Free Tool Strategy
$ npx skills add alirezarezvani/claude-skills --skill free-tool-strategy -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install alirezarezvani/claude-skills free-tool-strategy --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/alirezarezvani/claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/marketing-skill/skills/free-tool-strategy .claude/skills/free-tool-strategy && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "free-tool-strategy" agent skill from https://github.com/alirezarezvani/claude-skills/tree/main/marketing-skill/skills/free-tool-strategy into .claude/skills/free-tool-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "free-tool-strategy", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/alirezarezvani/claude-skills/tree/main/marketing-skill/skills/free-tool-strategyType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add alirezarezvani/claude-skills --skill free-tool-strategy -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install alirezarezvani/claude-skills free-tool-strategy --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/alirezarezvani/claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/marketing-skill/skills/free-tool-strategy .agents/skills/free-tool-strategy && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "free-tool-strategy" agent skill from https://github.com/alirezarezvani/claude-skills/tree/main/marketing-skill/skills/free-tool-strategy into .agents/skills/free-tool-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "free-tool-strategy", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add alirezarezvani/claude-skills --skill free-tool-strategy -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install alirezarezvani/claude-skills free-tool-strategy --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/alirezarezvani/claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/marketing-skill/skills/free-tool-strategy .cursor/skills/free-tool-strategy && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "free-tool-strategy" agent skill from https://github.com/alirezarezvani/claude-skills/tree/main/marketing-skill/skills/free-tool-strategy into .cursor/skills/free-tool-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "free-tool-strategy", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/alirezarezvani/claude-skills.git --path marketing-skill/skills/free-tool-strategy--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add alirezarezvani/claude-skills --skill free-tool-strategy -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install alirezarezvani/claude-skills free-tool-strategy --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/alirezarezvani/claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/marketing-skill/skills/free-tool-strategy .gemini/skills/free-tool-strategy && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "free-tool-strategy" agent skill from https://github.com/alirezarezvani/claude-skills/tree/main/marketing-skill/skills/free-tool-strategy into .gemini/skills/free-tool-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "free-tool-strategy", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install alirezarezvani/claude-skills free-tool-strategyInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add alirezarezvani/claude-skills --skill free-tool-strategy -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/alirezarezvani/claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/marketing-skill/skills/free-tool-strategy .github/skills/free-tool-strategy && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "free-tool-strategy" agent skill from https://github.com/alirezarezvani/claude-skills/tree/main/marketing-skill/skills/free-tool-strategy into .github/skills/free-tool-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "free-tool-strategy", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add alirezarezvani/claude-skills --skill free-tool-strategy -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install alirezarezvani/claude-skills free-tool-strategy --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/alirezarezvani/claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/marketing-skill/skills/free-tool-strategy .opencode/skills/free-tool-strategy && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "free-tool-strategy" agent skill from https://github.com/alirezarezvani/claude-skills/tree/main/marketing-skill/skills/free-tool-strategy into .opencode/skills/free-tool-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "free-tool-strategy", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
free-tool-strategy- GitHub stars
- 28k
- Token cost
- ~3.1k tokens
- SKILL.md length
- 1,559 words
- Files
- 4 (incl. scripts, references)
- Skills in repo
- 342
- Repo updated
- First seen
- Licence
- MIT
At a glance
When the user wants to build a free tool for marketing — lead generation, SEO value, or brand awareness.
- Works in 3 steps: Product & Audience → Resources → Goals
- Wants to build a free tool for marketing — lead generation
- SKILL.md covers Before Starting, How This Skill Works, Tool Types and When to Use Each and The 6-Factor Evaluation…, plus 8 more sections
- Runs Python scripts from its folder
What it does
Free Tool Strategy is an agent skill from alirezarezvani/claude-skills. When the user wants to build a free tool for marketing — lead generation, SEO value, or brand awareness. Use when they mention 'engineering as marketing,' 'free tool,' 'calculator,' 'generator,' 'checker,' 'grader,' 'marketing tool,' 'lead gen tool,' 'build something for traffic,' 'interactive tool,' or 'free resource.' Covers idea evaluation, tool design, and launch strategy. For pure SEO content strategy (no tool), use seo-audit or content-strategy instead.
Its SKILL.md is about 3.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including scripts and reference files (for example `references/launch-playbook.md`, `references/tool-types-guide.md` and `scripts/tool_roi_estimator.py`).
It sits in Marketing & SEO, covering Lead generation, Content strategy and SEO audit. The repository describes itself as: 380 Claude Code skills & agent skills & plugins (30+ Agents, 70+ custom commands, 380+ skills, customizable references, scripts)for Claude Code, Codex, Gemini CLI, Cursor, and 8… The licence is MIT.
When your agent uses it
- Wants to build a free tool for marketing — lead generation
- Brand awareness
- They mention engineering as marketing
- Build something for traffic
Example prompts
- “engineering as marketing,”
- “free tool,”
- “calculator,”
- “/free-tool-strategy”
Requirements
- Python 3
Workflow steps
3 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 19392f7. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 1 file in scripts/ (Python), which the agent can run.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Free Tool Strategy loads about 3.1k tokens when it runs, and up to ~7.4k if it reads all its reference files. Until then it costs about 121 tokens; SKILL.md has 1,559 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
SKILL.md
The full file from alirezarezvani/claude-skills at commit 19392f7, republished under its MIT licence (© alirezarezvani). 1,559 words, ~3,052 tokens.
Download SKILL.mdSave it as
.claude/skills/free-tool-strategy/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.- name
- free-tool-strategy
- description
- When the user wants to build a free tool for marketing — lead generation, SEO value, or brand awareness. Use when they mention 'engineering as marketing,' 'free tool,' 'calculator,' 'generator,' 'checker,' 'grader,' 'marketing tool,' 'lead gen tool,' 'build something for traffic,' 'interactive tool,' or 'free resource.' Covers idea evaluation, tool design, and launch strategy. For pure SEO content strategy (no tool), use seo-audit or content-strategy instead.
- license
- MIT
- metadata.version
- 1.0.0
- metadata.author
- Alireza Rezvani
- metadata.category
- marketing
- metadata.updated
- 2026-03-06
Free Tool Strategy
You are a growth engineer who has built and launched free tools that generated hundreds of thousands of visitors, thousands of leads, and hundreds of backlinks without a single paid ad. You know which ideas have legs and which waste engineering time. Your goal is to help decide what to build, how to design it for maximum value and lead capture, and how to launch it so people actually find it.
Before Starting
Check for context first:
If .claude/product-marketing-context.md exists, read it before asking questions. Use that context and only ask for information not already covered.
Gather this context (ask if not provided):
1. Product & Audience
- What's your core product and who buys it?
- What problem does your ideal customer have that a free tool could solve adjacently?
- What does your audience search for that isn't your product?
2. Resources
- How much engineering time can you dedicate? (Hours, days, weeks)
- Do you have design resources, or is this no-code/template?
- Who maintains the tool after launch?
3. Goals
- Primary goal: SEO traffic, lead generation, backlinks, or brand awareness?
- What does a "win" look like? (X leads/month, Y backlinks, Z organic visitors)
How This Skill Works
Mode 1: Evaluate Tool Ideas
You have one or more ideas and you're not sure which to build — or whether to build any of them.
Workflow:
- Score each idea against the 6-factor evaluation framework
- Identify the highest-potential idea based on your specific goals and resources
- Validate with keyword data before committing engineering time
Mode 2: Design the Tool
You've decided what to build. Now design it to maximize value, lead capture, and shareability.
Workflow:
- Define the core value exchange (what the user inputs → what they get back)
- Design the UX for minimum friction
- Plan lead capture: where, what to ask, progressive profiling
- Design shareable output (results page, generated report, embeddable badge)
- Plan the SEO landing page structure
Mode 3: Launch and Measure
You've built it. Now distribute it and track whether it's working.
Workflow:
- Pre-launch: SEO landing page, schema markup, submit to directories
- Launch channels: Product Hunt, Hacker News, industry newsletters, social
- Outreach: who links to similar tools? → build a link acquisition list
- Measurement: set up tracking for usage, leads, organic traffic, backlinks
- Iterate: usage data tells you what to improve
Tool Types and When to Use Each
| Tool Type | What It Does | Build Complexity | Best For |
|---|---|---|---|
| Calculator | Takes inputs, outputs a number or range | Low–Medium | LTV, ROI, pricing, salary, savings |
| Generator | Creates text, ideas, or structured content | Low (template) – High (AI) | Headlines, bios, copy, names, reports |
| Checker | Analyzes a URL, text, or file and scores/audits it | Medium–High | SEO audit, readability, compliance, spelling |
| Grader | Scores something against a rubric | Medium | Website grade, email grade, sales page score |
| Converter | Transforms input from one format to another | Low–Medium | Units, formats, currencies, time zones |
| Template | Pre-built fillable documents | Very Low | Contracts, briefs, decks, roadmaps |
| Interactive Visualization | Shows data or concepts visually | High | Market maps, comparison charts, trend data |
See references/tool-types-guide.md for detailed examples, build guides, and complexity breakdowns per type.
The 6-Factor Evaluation Framework
Score each idea 1–5 on each factor. Highest total = build first.
| Factor | What to Check | 1 (weak) | 5 (strong) |
|---|---|---|---|
| Search Volume | Monthly searches for "free [tool]" | <100/mo | >5k/mo |
| Competition | Quality of existing free tools | Excellent tools exist | No good free alternatives |
| Build Effort | Engineering time required | Months | Days |
| Lead Capture Potential | Can you naturally gate or capture email? | Forced gate, kills UX | Natural fit (results emailed, report downloaded) |
| SEO Value | Can you build topical authority + backlinks? | Thin, one-page utility | Deep use case, link magnet |
| Viral Potential | Will users share results or embed the tool? | Nobody shares | Results are shareable by design |
Scoring guide:
- 25–30: Build it, now
- 18–24: Strong candidate, validate keyword volume first
- 12–17: Maybe, if resources are low or it fits a strategic gap
- <12: Pass, or rethink the concept
Design Principles
Value Before Gate
Give the core value first. Gate the upgrade — the deeper report, the saved results, the email delivery. If the tool is only valuable after they give you their email, you've designed a lead form, not a tool.
Good: Show the score immediately → offer to email the full report Bad: "Enter your email to see your results"
Minimal Friction
- Max 3 inputs to get initial results
- No account required for the core value
- Progressive disclosure: simple first, detailed on request
- Mobile-optimized — 50%+ of tool traffic is mobile
Shareable Results
Design results so users want to share them:
- Unique results URL that others can visit
- "Tweet your score" / "Copy your results" buttons
- Embed code for badges or widgets
- Downloadable report (PDF or CSV)
- Social-ready image generation (score card, certificate)
Mobile-First
- Inputs work on touch screens
- Results render cleanly on mobile
- Share buttons trigger native share sheet
- No hover-dependent UI
Lead Capture — When, What, How
When to Gate
Gate with email when:
- Results are complex enough to warrant a "report" framing
- Tool produces ongoing value (track over time, re-run monthly)
- Results are personalized and users would naturally want to save them
Don't gate when:
- Core result is a single number or short answer
- Competition offers the same thing without a gate
- Your primary goal is SEO/backlinks (gates hurt time-on-page and links)
What to Ask
Ask the minimum. Every field drops completion by ~10%.
First gate: Email only Second gate (on re-use or report download): Name + Company size + Role
Progressive Profiling
Don't ask everything at once. Build the profile over multiple sessions:
- Session 1: Email to save results
- Session 2: Role, use case (asked contextually, not in a form)
- Session 3: Company, team size (if they request team features)
Show full SKILL.md (616 more words)Show less
SEO Strategy for Free Tools
Landing Page Structure
H1: [Free Tool Name] — [What It Does] [one phrase]
Subhead: [Who it's for] + [what problem it solves]
[The Tool — above the fold]
H2: How [Tool Name] works
H2: Why [audience] use [tool name]
H2: [Related Question 1]
H2: [Related Question 2]
H2: Frequently Asked QuestionsTarget keyword in: H1, URL slug, meta title, first 100 words, at least 2 subheadings.
Schema Markup
Add SoftwareApplication schema to tell Google what the page is:
{
"@type": "SoftwareApplication",
"name": "Tool Name",
"applicationCategory": "BusinessApplication",
"offers": {"@type": "Offer", "price": "0"},
"description": "..."
}Link Magnet Potential
Tools attract links from:
- Resource pages ("best free tools for X")
- Blog posts ("the tools I use for X")
- Subreddits, Slack communities, Facebook groups
- Weekly newsletters in your niche
Plan your outreach list before launch. Who writes about tools in your category? Find their existing "best tools" posts and reach out post-launch.
Measurement
Track these from day one:
| Metric | What It Tells You | Tool |
|---|---|---|
| Tool usage (sessions, completions) | Is anyone using it? | GA4 / Plausible |
| Lead conversion rate | Is it generating leads? | CRM + GA4 events |
| Organic traffic | Is it ranking? | Google Search Console |
| Referring domains | Is it earning links? | Ahrefs / Google GSC |
| Email to paid conversion | Is it generating pipeline? | CRM attribution |
| Bounce rate / time on page | Is the tool actually used? | GA4 |
Targets at 90 days post-launch:
- Organic traffic: 500+ sessions/month
- Lead conversion: 5–15% of completions
- Referring domains: 10+ organic backlinks
Run scripts/tool_roi_estimator.py to model break-even timeline based on your traffic and conversion assumptions.
Proactive Triggers
Surface these without being asked:
- Tool requires account before use → Flag and redesign the gate. This kills SEO, kills virality, and tells users you're harvesting data, not providing value.
- No shareable output → If results exist only in the session and can't be shared or saved, you've built half a tool. Flag the missed virality opportunity.
- No keyword validation → If the tool concept hasn't been validated against search volume before build, flag — 3 hours of research beats 3 weeks of building a tool nobody searches for.
- Competitors with the same free tool → If an existing tool is well-established and free, the bar is "10x better or don't build it." Flag the competitive risk.
- Single input → single output → Ultra-simple tools lose SEO value quickly and attract no links. Flag if the tool needs more depth to be link-worthy.
- No maintenance plan → Free tools die when the API they call changes or the logic gets stale. Flag the need for a maintenance owner before launch.
Output Artifacts
| When you ask for... | You get... |
|---|---|
| "Evaluate my tool ideas" | Scored comparison matrix (6 factors × ideas), ranked recommendation with rationale |
| "Design this tool" | UX spec: inputs, outputs, lead capture flow, share mechanics, landing page outline |
| "Write the landing page" | Full landing page copy: H1, subhead, how it works section, FAQ, meta title + description |
| "Plan the launch" | Pre-launch checklist, launch channel list with specific actions, outreach target list |
| "Set up measurement" | GA4 event tracking plan, GSC setup checklist, KPI targets at 30/60/90 days |
| "Is this tool worth building?" | ROI model (using tool_roi_estimator.py): break-even month, required traffic, lead value threshold |
Communication
All output follows the structured communication standard:
- Bottom line first — recommendation before reasoning
- Numbers-grounded — traffic targets, conversion rates, ROI projections tied to your inputs
- Confidence tagging — 🟢 validated / 🟡 estimated / 🔴 assumed
- Build decisions are binary — "build it" or "don't build it" with a clear reason, not "it depends"
Related Skills
- seo-audit: Use for auditing existing pages and keyword strategy. NOT for building new tool-based content assets.
- content-strategy: Use for planning the overall content program (blogs, guides, whitepapers). NOT for tool-specific lead generation.
- copywriting: Use when writing the marketing copy for the tool landing page. NOT for the tool UX design or lead capture strategy.
- launch-strategy: Use when planning the full product or feature launch. NOT for tool-specific distribution (use free-tool-strategy for that).
- analytics-tracking: Use when implementing the measurement stack for the tool. NOT for deciding what to measure (use free-tool-strategy for that).
- form-cro: Use when optimizing the lead capture form in the tool. NOT for the tool design or launch strategy.
© alirezarezvani, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 3 other files (scripts, references) in marketing-skill/skills/free-tool-strategy of alirezarezvani/claude-skills.
- SKILL.md
- references/launch-playbook.md
- references/tool-types-guide.md
- scripts/tool_roi_estimator.py
Open the folder on GitHubat commit 19392f7
Compare with similar skills
Free Tool Strategy next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Free Tool Strategy this skillalirezarezvani/claude-skills | 28k | — | ~3.1k | Automated safety check: Pass | MIT | |
| E2E SEO Assistantirinabuht12-oss/marketing-skills | 4.1k | — | ~1.9k | Automated safety check: Pass | None | |
| SEO Auditmagnus919/hermes-profiles | 289 | — | ~1k | Automated safety check: Pass | MIT | |
| SEO Performance Reviewfjrevoredo/mini-diarium | 309 | — | ~3k | Automated safety check: Pass | MIT | |
| Campaign Planrongxinzy/RongxinAI | 154 | 1 repos | ~3.6k | Automated safety check: Pass | Apache-2.0 | |
| SEO Keyword ClusteringAgriciDaniel/claude-seo | 19k | 2 repos | ~3.3k | Automated safety check: Pass | MIT |
Similar skills
SEO Audit
magnus919/hermes-profiles
Full-spectrum SEO + AEO audit skill — technical crawl analysis, on-page content optimization, structured data (JSON-LD/Schema.org) validation, Ghost CMS metadata completion, answer engine…
SEO Performance Review
fjrevoredo/mini-diarium
Applies to Mini Diarium's marketing site (website/) and its SEO data under docs/seo/.
Campaign Plan
rongxinzy/RongxinAI
Generate a full campaign brief with objectives, audience, messaging, channel strategy, content calendar, and success metrics.
SEO Keyword Clustering
AgriciDaniel/claude-seo
Clusters keywords by how much their search results overlap and designs a hub-and-spoke content plan with an internal link matrix and an interactive cluster map.
SEO Content Brief Generator
AgriciDaniel/claude-seo
Builds research-backed SEO content briefs with competitor scoring, per-section word counts and page-type templates, for new pages or improving existing ones.
More from alirezarezvani/claude-skills
All 342 skills in this repoAgile Product Owner
alirezarezvani/claude-skills
Writes INVEST-checked user stories with acceptance criteria, splits epics, plans sprints from velocity and ranks the backlog with a weighted score.
Product Strategist
alirezarezvani/claude-skills
OKR cascade toolkit for product leaders: generates aligned company-to-team OKRs from five strategy types and scores how well they line up.
App Store Optimization
alirezarezvani/claude-skills
App Store Optimization (ASO) toolkit for researching keywords, analyzing competitor rankings, generating metadata suggestions, and improving app visibility on Apple App Store and Google Play Store.
AWS Solution Architect
alirezarezvani/claude-skills
Design AWS architectures for startups using serverless patterns and IaC templates.
Campaign Analytics
alirezarezvani/claude-skills
Calculates attribution, funnel and ROI figures for marketing campaigns with three Python scripts that need only the standard library.
Code to PRD
alirezarezvani/claude-skills
Reverse-engineers a frontend, backend or fullstack codebase into a product requirements document with per-page docs, an enum dictionary and an API inventory.
Related
Categories
Questions about Free Tool Strategy
What does Free Tool Strategy do?
When the user wants to build a free tool for marketing — lead generation, SEO value, or brand awareness. Free Tool Strategy is an agent skill from alirezarezvani/claude-skills. When the user wants to build a free tool for marketing — lead generation, SEO value, or brand awareness.
When should I use Free Tool Strategy?
Free Tool Strategy fits situations like: wants to build a free tool for marketing — lead generation; brand awareness; they mention engineering as marketing; build something for traffic.
How do I install Free Tool Strategy in Claude Code?
Run `npx skills add alirezarezvani/claude-skills --skill free-tool-strategy -a claude-code`. Or copy the skill folder (marketing-skill/skills/free-tool-strategy in alirezarezvani/claude-skills) into .claude/skills/free-tool-strategy in your project. Claude Code loads it when a task matches its description.
How do I install Free Tool Strategy in Codex?
Run `npx skills add alirezarezvani/claude-skills --skill free-tool-strategy -a codex`. Or copy the skill folder (marketing-skill/skills/free-tool-strategy in alirezarezvani/claude-skills) into .agents/skills/free-tool-strategy in your project. Codex loads it when a task matches its description.
Can I use Free Tool Strategy in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add alirezarezvani/claude-skills --skill free-tool-strategy -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/free-tool-strategy, .gemini/skills/free-tool-strategy, .github/skills/free-tool-strategy and .opencode/skills/free-tool-strategy in your project.
What does Free Tool Strategy need to run?
Going by SKILL.md and its folder, Free Tool Strategy needs Python for the scripts in its folder. Our summary lists: Python 3.
Does Free Tool Strategy access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Free Tool Strategy safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Free Tool Strategy use?
Free Tool Strategy is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Free Tool Strategy use?
About 3.1k tokens (SKILL.md is roughly 12k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 4.4k tokens, read only when the agent opens those files.
What are the alternatives to Free Tool Strategy?
Skills that share tags, products or a category with Free Tool Strategy: E2E SEO Assistant (irinabuht12-oss/marketing-skills, 4.1k stars), SEO Audit (magnus919/hermes-profiles, 289 stars), SEO Performance Review (fjrevoredo/mini-diarium, 309 stars) and Campaign Plan (rongxinzy/RongxinAI, 154 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Free Tool Strategy?
alirezarezvani (a GitHub user) maintains it in alirezarezvani/claude-skills, which has 27,938 GitHub stars. The repository holds 342 skills in this directory. The repository was last updated on August 30, 2026.
Source: alirezarezvani/claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.