agentleFS
sametcelikbicaksametcelikbicak/opencode-team/skills/team-marketing/SKILL.md

team-marketing

Skill69 starsChanged 19 days agoMITView on GitHub

Marketing and launch methodology. Positioning, message framework, channel plan, launch copy, measurable metrics. The playbook of the marketing role.

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Test: can the target audience reading this sentence say "this is for me"?

    line 17
  2. Distinctive:

    Do not estimate the segment size.

    line 36
  3. Distinctive:

    Do not advertise first. Start with the owned channel.

    line 50
  4. Distinctive:

    If "Try free" requires a card, do not hide this.

    line 65

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Marketing and Launch

1. Positioning

One sentence, three parts:

For [target audience], [problem solution], thanks to [difference from the competitor].

Bad: "Our app is a modern, fast and user-friendly invoice tracking solution." Good: "An invoice tracking tool for freelance graphic designers that automates email reminders, without QuickBooks' accounting complexity."

Test: can the target audience reading this sentence say "this is for me"? If not, narrow the target audience.

2. Message framework

LayerContent
Main promise"[Problem] is now [outcome]"
Support 1Highlighted feature (in benefit language)
Support 2Trust signal (privacy, price, ease of setup)
Support 3Proof (user count, measurement, reviews — do not write it without proof)
Objection handling"[Most likely objection] — [response]"

Benefit language example: feature → "Cuts monthly billing from 2 hours down to 10 minutes."

3. Target audience

SegmentSizeWhere to find themBudgetPriority

Do not estimate the segment size; write "estimated".

4. Channel plan

Prioritize free or cheap channels. Order: owned channel (production) → community → direct outreach → partnerships → paid.

ChannelFormatFrequencyWhoMetricPriority
Reddit (relevant subreddit)value-adding post1 per weekfoundercomments + clicks1
Product Huntlaunch pagelaunch dayfounderdaily ranking2
LinkedInshort case study2 per monthfounderreach + site traffic3

For each channel: what will be published (format + message), when, how success is measured.

Do not advertise first. Start with the owned channel.

5. Landing page copy

[Headline] — the main promise, concrete
[Subheadline] — for whom, how
[Benefit list] — 3 items, each concrete
[How it works] — 3 steps
[CTA] — a single action ("Start free"), no second CTA
[Trust] — price, privacy, no card required

Rules:

  • One CTA. If there are two buttons, one of them is not dominant.
  • If "Try free" requires a card, do not hide this; it destroys trust.
  • A benefit list, not a feature list.

6. Product announcement copy

Short. 100-150 words. What you do, for whom, how to get to it.

Verify competitor names, prices and market data with websearch. Do not make up data you could not verify; write "unverifiable".

7. Metrics

MetricBaselineTargetToolWhen it is measured

It must be measurable. Not "increase", but "a 25% increase" (relative to which metric?).

Tool suggestions (free): PostHog (1M events/month), Umami (self-hosted), GA4, Plausible CE, Cloudflare Web Analytics.

8. Publishing calendar

DateChannelContentStatus

Common mistakes

MistakeThe right way
A feature listA benefit list
Jargon ("solution", "platform", "ecosystem")The user's own words
Made-up numbers ("10,000 users")Do not write it without proof
8 channels with no consistency in any of them2-3 channels, consistent
An unmeasurable targetWrite a number or say "to be determined"
Making up the launch dateSay "proposed", put it in the list of open questions

Output format

Markdown: Positioning / Message framework / Target audience / Channel plan / Landing page copy / Announcement copy / Metrics / Publishing calendar / Open questions.

In the user's language (Turkish or English).

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.