本文へ移動
cccskills
無料GitHub で公開

suede-free-tools

Suede-affiliated engineering-as-marketing strategy for selecting, scoring, and scoping calculators, graders, generators, and other free interactive tools. Use when the user wants a lead, link, education, or product-adoption asset with a measurable path to the paid product. NOT FOR: downloadable lead assets (use suede-lead-magnets), implementation of a full website (use suede-site-alchemy), or search diagnostics (use suede-seo-audit).

インストール方法を見る

含まれるファイル(5)

  • SKILL.md8.6 KB
  • agents/openai.yaml606 B
  • CARD.md4.3 KB
  • evals/evals.json6.1 KB
  • references/tool-types.md3.9 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Suede Free-Tool Growth Strategy

Suede uses engineering as marketing when a genuinely useful tool can create qualified discovery and a natural bridge to the paid product. Select, score, and scope the smallest maintainable calculator, grader, generator, or utility whose output earns attention rather than merely capturing it.

Initial Assessment

Check for product marketing context first: If .agents/product-marketing.md exists (or .claude/product-marketing.md, or the legacy product-marketing-context.md filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.

Before designing a tool strategy, understand:

  1. Business Context - What's the core product? Who is the target audience? What problems do they have?

  2. Goals - Lead generation? SEO/traffic? Brand awareness? Product education? What is one lead worth (LTV and close rate from this source)?

  3. Resources - Technical capacity to build? Ongoing maintenance bandwidth? Budget for promotion? Timeline?

  4. Existing Behavior - What tools or manual workarounds does the audience use today? How are leads generated now?


Core Principles

1. Solve a Real Problem

  • Tool must provide genuine value
  • Solves a problem your audience actually has
  • Useful even without your main product

2. Adjacent to Core Product

  • Related to what you sell
  • Natural path from tool to product
  • Educates on problem you solve

3. Simple and Focused

  • Does one thing well
  • Low friction to use
  • Immediate value

4. Worth the Investment

  • Lead value × expected leads > build cost + maintenance

Populate all four terms before calling the go/no-go, and show the arithmetic:

  • Lead value = customer LTV × close rate for this lead source, from the intake numbers.
  • Expected leads = monthly search volume for the SEO target keyword × a stated visit-to-use rate × a stated use-to-capture rate.
  • Build cost = the MVP scope below, in engineer-days.
  • Maintenance = engineer-days per quarter to keep data, dependencies, and the hosting current.

State every rate you assumed and where it came from. If a term cannot be sourced, say which one and mark the go/no-go unresolved rather than filling it in.


Tool Types Overview

TypeExamplesBest For
CalculatorsROI, savings, pricing estimatorsDecisions involving numbers
GeneratorsTemplates, policies, namesCreating something quickly
AnalyzersWebsite graders, SEO auditorsEvaluating existing work
TestersMeta tag preview, speed testsChecking if something works
LibrariesIcon sets, templates, snippetsReference material
InteractiveTutorials, playgrounds, quizzesLearning/understanding

For detailed tool types and examples: See references/tool-types.md


Ideation Framework

Start with Pain Points

  1. What problems does your audience Google? - Search query research, common questions

  2. What manual processes are tedious? - Spreadsheet tasks, repetitive calculations

  3. What do they need before buying your product? - Assessments, planning, comparisons

  4. What information do they wish they had? - Data they can't easily access, benchmarks

Validate the Idea

  • Search demand: Is there search volume? How competitive?
  • Uniqueness: What exists? How can you be 10x better?
  • Lead quality: Does this audience match buyers?
  • Build feasibility: How complex? Can you scope an MVP?

Lead Capture Strategy

Gating Options

ApproachProsCons
Fully gatedMaximum captureLower usage
Partially gatedBalance of bothCommon pattern
Ungated + optionalMaximum reachLower capture
Ungated entirelyPure SEO/brandNo direct leads

Lead Capture Best Practices

  • Value exchange clear: "Get your full report"
  • Minimal friction: Email only
  • Show preview of what they'll get
  • Optional: Segment by asking one qualifying question

The gating trade-off itself (per-field conversion cost and how to frame the exchange) is owned by suede-lead-magnets. Use its gating tables when deciding what to ask for; the table above only covers where the gate sits in a tool.


SEO Considerations

Keyword Strategy

Tool landing page: "[thing] calculator", "[thing] generator", "free [tool type]"

Supporting content: "How to [use case]", "What is [concept]"

Link Building

Free tools attract links because:

  • Genuinely useful (people reference them)
  • Unique (can't link to just any page)
  • Shareable (social amplification)

Build vs. Buy

Build Custom

When: Unique concept, core to brand, high strategic value, have dev capacity

Use No-Code Tools

Options: Outgrow, Involve.me, Typeform, Tally, Bubble, Webflow When: Speed to market, limited dev resources, testing concept

Embed Existing

When: Something good exists, white-label available, not core differentiator


MVP Scope

Minimum Viable Tool

  1. Core functionality only: does the one thing, works reliably
  2. Essential UX: clear input, obvious output, mobile works
  3. Basic lead capture: email collection, leads go somewhere useful

What to Skip Initially

Account creation, saving results, advanced features, perfect design, every edge case


Evaluation Scorecard

Rate each factor 1-5:

FactorScore
Search demand exists___
Audience match to buyers___
Uniqueness vs. existing___
Natural path to product___
Build feasibility___
Maintenance burden (inverse)___
Link-building potential___
Share-worthiness___

25+: Strong candidate | 15-24: Promising | <15: Reconsider

Anchors for the three decisive factors: score these against the anchor, not on impression, and cite the evidence used:

Factor135
Search demand existsNo query with measurable volumeA query family in the hundreds of searches/monthA head term in the thousands/month
Build feasibilityNeeds a data pipeline, licensed data, or an ongoing integrationTwo to four engineer-weeks with known componentsOne engineer-week, one screen, no backend state
Maintenance burden (inverse)Depends on data refreshed on a schedule or a third-party APIOccasional content or dependency updatesStatic computation, nothing to refresh

Output Format

Return exactly these sections:

1. Recommended Tool

Name and the one-sentence job it does for the user.

2. Scorecard

The filled table with a score per factor, the total, and the verdict band. For the three anchored factors, name the evidence behind the score.

3. MVP Scope

Two explicit lists: In (what v1 does) and Out (what is deliberately deferred). No item appears in both.

4. Gating Decision

Which option from Gating Options, and the trade-off accepted in one line.

5. SEO Target

The single target query for the tool page, plus the supporting-content query.

6. Instrumentation Handoff

The two or three usage events the tool must emit (use, complete, capture) so suede-analytics can read the funnel. This skill does not define the metrics plan itself.


Boundaries

  • Do not claim search demand, lead volume, link potential, or build feasibility without evidence and dated assumptions.
  • Do not build, deploy, publish, collect leads, or connect production data unless the user authorizes implementation.
  • Do not invent tool outputs or use a calculator as disguised professional, legal, medical, or financial advice.
  • Do not decide pricing, data-retention, or consent policy for the user.

Routing

  • Use suede-lead-magnets for downloadable assets and suede-site-alchemy for the public conversion surface.
  • Use suede-seo-audit for search validation and suede-analytics for usage measurement.
  • Use suede-emails for the post-capture lifecycle sequence.
  • Use suede-content-strategy for the supporting content around the tool page.
  • Use suede-ads and suede-social for tool distribution and launch promotion.
  • Use suede-ab-testing to design and evaluate tests on the tool page or its gate.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Suede-affiliated Amazon money-recovery audit for restocking fees, short or denied refunds, and Amazon-billed subscriptions. Use when the user mentions a restocking fee, a short or denied Amazon refund, or a forgotten Prime Video Channel, Audible, Kindle Unlimited, or Prime charge, or asks whether Amazon still owes or bills them. Read-only discovery; no chat, cancellation, or dispute without the account owner's per-item confirmation, and never a promise of recovery. Requires an authenticated Claude in Chrome session. NOT FOR: bank chargebacks, marketplace A-to-z seller claims, price-protection claims, or subscriptions billed outside Amazon (use subscription-recovery).

日本語の概要は準備中です。原文の説明を表示しています。

JasonColapietro/suede-creator-skills1272026年10月12日 更新

Suede Labs Android app factory: plan, build, test, and release a production-grade native Android app from a product idea through Google Play. Use for requests to create, ship, submit, monetize, or modernize an Android app. Covers Kotlin and Jetpack Compose architecture, API-level policy verification, accessibility, privacy and Data Safety, Play Billing, Play Integrity, account deletion, testing, performance, store assets, signing, staged rollout, and a release evidence gate. NOT FOR: iOS work (private Suede Labs companion, not in this pack: ios-app-factory), a review-only pass on an existing app (use suede-code-review), or live Play listing and keyword audits on a shipped app (use suede-aso).

日本語の概要は準備中です。原文の説明を表示しています。

JasonColapietro/suede-creator-skills1272026年10月12日 更新

Design, review, and visually QA web and app interfaces against explicit design laws so shipped screens look intentional instead of generic AI output.

日本語の概要は準備中です。原文の説明を表示しています。

JasonColapietro/suede-creator-skills1272026年10月12日 更新

Suede AI full-stack surface builder that runs design, copy, and visual QA as one pass: landing pages, brand surfaces, product UI, dashboards, campaigns, launch pages, and reference-to-target restyles (suedify). Use when a build needs layout and words together, when a redesign or launch surface has to ship end to end, when the request is 'make this site look like that one', or when design, copy, asset, and QA lanes have to move at once. NOT FOR: a design-token, dark-mode, or single-component decision (use suede-design); copy with no layout work (use johnny-suede-write, or suede-copy for one standalone conversion surface); conversion and funnel architecture (use suede-site-alchemy); multi-agent orchestration protocols, WIP protection, and rollback trees (use suede-agent-teams).

日本語の概要は準備中です。原文の説明を表示しています。

JasonColapietro/suede-creator-skills1272026年10月12日 更新

Suede Labs full writing stack: sharper copy for docs, pages, email, social, headlines, CTAs, product listings, and public explainers, with an SEO/AEO/AI EO pass, persona and framework selection, brand-voice alignment, and a scored ship gate. Use when a writing job spans more than one surface, needs a voice retune as well as a draft, needs discoverability metadata alongside the copy, when the document is one an agent reads such as a SKILL.md, CLAUDE.md, or AGENTS.md, or when the user asks for 'the full writing stack', a launch package, or a public explainer talk-track. NOT FOR: one standalone conversion surface in one pass (use suede-copy); stripping AI patterns from text you did not write (use suede-deslop); a researched multi-phase piece for a high-stakes public surface (use suede-ship-copy); a deep standalone SEO audit (use suede-seo-audit); copy that ships inside a design or layout build (use johnny-suede-design).

日本語の概要は準備中です。原文の説明を表示しています。

JasonColapietro/suede-creator-skills1272026年10月12日 更新

Suede Labs workflow for turning a website, PWA, dashboard, or marketplace into an iOS app. Use when the user has a live site or web app and asks to put it on the App Store, wrap it in an app, ship an iOS version, or convert a PWA to native, covers URL audit, shell-vs-native strategy, App Store 4.2 wrapper risk, native value requirements, screenshots, metadata, privacy answers, and the release gate. NOT FOR: building a native iOS app with no existing site (private Suede Labs companion, not in this pack: ios-swiftui-product); repairing or releasing an existing Capacitor shell (private Suede Labs companion, not in this pack: ios-capacitor-shell); Android conversions (use android-app-factory); live listing and keyword audits on a shipped app (use suede-aso).

日本語の概要は準備中です。原文の説明を表示しています。

JasonColapietro/suede-creator-skills1272026年10月12日 更新

JasonColapietro のスキルをすべて見る

このスキルの問題を報告する