Skill: Analytics Review

Purpose

Score last week's posts and salon outreach against KPIs. Push learnings to MEMORY.md. Feed salon-funnel back to sales-bd.

Inputs

• Emir pastes weekly LinkedIn analytics into data/imports/analytics_YYYY-MM-DD.md
• Own outputs/ from the same week
• Salon outreach reply log from data/imports/outreach_replies_YYYY-MM-DD.md

Process

1. Match each published post in analytics to its draft. Flag unpublished drafts.
2. Compute: reactions, comments, reshares, impressions per post. Avg + median.
3. Identify top 1 and bottom 1. Extract patterns.
4. Outreach funnel:
   • Connect requests sent / accepted / response rate
   • DMs sent / replied / qualified (handed to sales-bd)
5. Update MEMORY.md on confirmed patterns (>=2 posts).
6. Write report to outputs/YYYY-MM-DD_analytics.md.
7. Push salon-funnel summary to agents/sales-bd/ journal.

Report Template

# Analytics — Week of YYYY-MM-DD

## Scoreboard
| Post | Reactions | Comments | Impressions | Status |
|------|-----------|----------|-------------|--------|

## Top post
- Slug, hook, why it worked

## Bottom post
- Slug, hook, hypothesized cause

## Trailing KPIs (4-week rolling)
| Metric | Target | 4wk avg |
|--------|--------|---------|

## Salon B2B funnel
- Connects sent / accepted / rate
- DMs sent / replied / qualified
- Names handed to sales-bd

## Memory updates
- <pattern added/removed>

## Next week
- 1-2 specific experiments

Quality Bar

• Pattern enters MEMORY only after 2 confirming posts
• Anti-pattern after 2 confirming bottom posts
• Salon-funnel handoff to sales-bd is mandatory — never skip
• Report fits on one screen

Skill: Comment Engine

Purpose

Draft 3-5 comments per day for Emir on relevant posts: founders, marketplace operators, beauty-tech, VC partners, ecosystem accelerators.

Targeting

• Founders in marketplace / beauty / health-tech — priority 1
• VC partners (SuperSeed, 500 LATAM, Turkish funds) — priority 1
• Founder Institute / Stripe / Cloudflare / Algolia ecosystem accounts — priority 2
• Salon owners with high follower counts in Turkey — priority 2
• Press / industry journalists covering Turkey startups — priority 3

Process

1. Emir pastes 5-10 post URLs into data/imports/comment_queue.md OR agent monitors a watchlist of authors.
2. Per post, draft a 1-3 sentence comment that:
   • Adds one specific data point, story, or counter-example
   • Does not pitch glossgo unless the post explicitly invites it
   • Carries Emir's founder voice (direct, market-data-anchored)
3. Save to outputs/YYYY-MM-DD_comments.md.

Comment Patterns That Compound

• Founder-receipt: "We saw this exact thing at glossgo when we tried . ."
• Market-frame: "Turkey data point on this: . ."
• Counter: respectful disagreement with one-line reasoning
• Extension: name a tool / pattern / framework the OP missed

Banned

• "Great post!", "100%", "So true"
• Anything that reads as an LLM auto-comment
• Pitching glossgo on a post that has nothing to do with marketplaces / beauty / Turkey

Output Template

# Comments YYYY-MM-DD

## <post URL or author>
**Type**: founder-receipt | market-frame | counter | extension
**Draft**:
> <comment text>
**Why**: <one-line reason this adds value>
**Notes for Emir**: <any caveat>

Skill: Founder Narrative

Purpose

Convert real founder moments — decisions, mistakes, pivots, conversations, events — into a high-trust LinkedIn post that builds Emir's authority and surfaces inbound.

When to Use

• Plan slot tagged angle: founder narrative
• A non-obvious decision was just made (architecture, hiring, pricing, GTM)
• An event happened where Emir or Bilal represented glossgo (Stripe Sessions, Founder Institute, partner meetings)
• An honest failure can be shared without harming customers, team, or fundraising

Process

1. Pull the source moment from journal/ or Emir's notes.
2. Strip to one decision or one realization. Discard sub-plots.
3. Write in first-person past tense. Start with the moment, not the conclusion.
4. End with the lesson or the open question. Avoid victory laps.
5. If the moment involves a teammate, name them only with consent (check journal for consent: ok).

Templates

Decision under pressure

Last Tuesday we had to choose between <A> and <B>.
The case for <A>: <one line>.
The case for <B>: <one line>.
We picked <B>. Three reasons:
1. <line>
2. <line>
3. <line>
What we learned in week one: <one line>.

Honest mistake

We spent 6 weeks on <X>. It didn't work.
Here is what we missed:
<one line on the missed signal>
What we are doing next: <one line>.

Quality Bar

• One central decision or realization
• Specific date or timeframe
• A lesson the reader can use
• No victory lap, no "and that's why we are amazing"
• No quoted numbers without source check

Skill: Market Lens

Purpose

Use Turkey beauty / marketplace market data to write a post that frames glossgo's opportunity. Highest format for reaching investors and ecosystem partners.

When to Use

• Plan slot tagged angle: market lens
• A market-research or competitive-intel output just landed with a fresh number
• A new external data point (industry report, macro shift, regulation) is relevant

Process

1. Pull source from agents/market-research/outputs/ or agents/competitive-intel/outputs/. Cite the path.
2. Pick exactly one statistic or one trend. Discard the rest.
3. Frame in 3 beats: market state → why current solutions fall short → where glossgo's wedge is.
4. Tie to a specific glossgo capability already on the bio (AI features, location-based, real-time pricing, verified reviews).
5. Close with a forward-looking question or a single sharp claim.

Templates

Single-stat market frame

Turkey's beauty market is $7.5B.
100K+ salons. <X>% are still digitized.

That means <implication in one line>.

What we are building at glossgo: <one line tied to the gap>.

Counter-narrative

The common take on Turkey marketplaces: <line>.
The data we keep seeing: <line>.
What changes if the data is right: <line>.

Quality Bar

• Source path cited in ## Notes
• One statistic, max two
• No competitor named
• The "wedge" line must reference a glossgo capability already public
• Forward-looking close, not a victory lap

Skill: Post Drafting

Purpose

Turn one plan slot into a publish-ready draft in Emir's voice.

Process

1. Read the plan row — angle, hook seed, anchor, day/time, language.
2. Write the hook (line 1, <=90 chars). Banned-opener scan.
3. Draft body (<=200 words). One central claim. One number. Founder-narrative arrow format permitted in max one block.
4. CTA only if there is a real ask (book a demo, comment with a stat, etc.). Otherwise close with a single declarative line.
5. 0-3 hashtags. No more.
6. Suggest image brief if the angle benefits visually. JSON skeleton inline.
7. Save to outputs/YYYY-MM-DD_post_<slug>.md. Mark status: ready_for_review.

Draft Template

# Post: <slug>
- Status: ready_for_review
- Day/time: <day> <HH:MM TRT>
- Language: EN | TR
- Anchor: <number or event>
- Expected reactions: <N>

## Hook
<line 1>

## Body
<<=200 words>

## Hashtags
#tag1 #tag2

## Image brief (optional)
{"style": "...", "subject": "...", "format": "1:1 LinkedIn"}

## Notes for Emir
- Why this hook
- Source path for every cited number
- Pre-clear status with investor-relations / sales-bd if applicable

Quality Bar

• Read-aloud test: founder voice, not brand voice
• Numbers test: every number traced to a knowledge/ or agents/<x>/outputs/ path in ## Notes
• Banned-opener scan
• Length test: hook <=90 chars, body <=200 words
• Competitor scan: no Fresha / Booksy / randevu.com / Kolay Randevu / Salon Randevu by name

Skill: Post Planning

Purpose

Produce a 7-day post plan with 2-3 slots filled, anchored to glossgo milestones, market data, and the salon B2B funnel.

Process

1. Pull last 7 days of journal/ — salon signups, partner news, events (Stripe Sessions, Founder Institute), press, product launches.
2. Pull latest data-bi, market-research, competitive-intel, sales-bd outputs. Extract numbers cleared as public (public_ok: true or already on the public bio).
3. Check knowledge/STRATEGY.md for quarter themes.
4. For each slot (2-3 / week):
   • Pick angle: (a) founder narrative, (b) market lens, (c) milestone, (d) salon-owner targeted, (e) reactive (event or partner).
   • Pick hook seed from MEMORY.md.
   • Pick day + time (Tue/Thu/Sat morning default).
   • Anchor: one number or one event.
   • Language: English unless angle = salon-owner-targeted (then Turkish).
5. Leave 1 slot open for reactive content. Write to outputs/YYYY-MM-DD_weekly_plan.md.

Output Template

# Week of YYYY-MM-DD

| Day | Time (TRT) | Angle | Lang | Hook seed | Anchor | Image | Status |
|-----|------------|-------|------|-----------|--------|-------|--------|
| Tue | 09:30 | market lens | EN | "85% of bookings still happen over DMs" | market-research output | Yes (card) | drafted |
| Thu | 10:00 | founder narrative | EN | "We almost shipped the wrong feature..." | journal entry | No | brief |
| Sat | 09:00 | salon-owner | TR | "Salon sahibi 3 saatini..." | sales-bd output | Yes | open |

Quality Bar

• Every filled slot has an anchor (number or event). No abstract opinion posts.
• No two consecutive posts in the same angle.
• At least one post / week targets the salon B2B audience.
• At least one post / week ties back to a glossgo milestone or metric.

Skill: Profile Rewrite

Purpose

Quarterly full-profile audit + rewrite for Emir. Aligns headline, About, Experience, Featured, Skills, and custom URL with glossgo growth phase and the founder/CMO positioning.

When to Use

• First-time setup
• Quarterly (every 90 days)
• After a material event (raise close, major partner, press hit, GTM milestone)

Inputs

• Current LinkedIn snapshot in data/imports/profile_snapshot_YYYY-MM-DD.md
• Latest MEMORY.md voice anchors
• knowledge/BRAND.md, knowledge/STRATEGY.md, knowledge/AUDIENCE.md
• Latest market-research and sales-bd outputs

Process

1. Read current snapshot. Section-by-section score (keep / sharpen / replace).
2. Pre-clear any new metric with investor-relations (raise-related) or sales-bd (pipeline-related).
3. Draft each section per template below.
4. Save to outputs/YYYY-MM-DD_profile_rewrite.md.
5. Emir updates LinkedIn manually. Log applied diff back to journal.

Section Templates

Headline (220 char cap)

Pattern: Co-founder & CMO @ glossgo · <Market frame> · <Specific traction>. Bio currently leads with this — keep + sharpen the third clause.

Custom URL

Current: linkedin.com/in/abbasemirozturk. Recommend: keep (rebranding mid-funnel hurts SEO + recognition).

About (2600 char cap, 7-step)

1. Hook (one declarative line, market-data anchored)
2. The market gap (one paragraph, no fluff)
3. What glossgo is (one paragraph, product-specific)
4. What we have done — receipts (arrow bullets, every claim verifiable)
5. Who I am + what I owned before (digital marketing background, Neolife / Rapid / arabam.com)
6. Who I want to hear from (salon operators, marketplace founders, investors, ecosystem partners — be specific)
7. CTA + URL

Featured (4 slots)

• glossgo.com (main landing)
• glossgo compare (price comparison)
• glossgo investment (data room / pitch link)
• One press hit or photo post (Stripe Sessions / Founder Institute)

Experience block (glossgo CMO)

• What you own: 5 arrow bullets (GTM, B2B salon, brand, lifecycle, launch coord)
• Receipts: $300K+ credits, 12+ partnerships, Founder Institute, Stripe Sessions, KVKK compliance, 99.9% uptime — only what is already public
• Team size + bootstrapped status (already public)

Skills (top 5, pinned)

• Marketplace Strategy
• Go-to-Market Strategy
• Digital Marketing
• Brand Strategy
• Growth (or Lifecycle Marketing)

Quality Bar

• Headline + About lead with glossgo, not past employer
• Every number is in knowledge/ or already public on bio / glossgo.com
• Banned-opener scan (no "Excited", "Thrilled", "Reflecting on")
• No competitor by name
• Profile reads as a single voice consistent with weekly posts

Skill: Salon B2B Outreach

Purpose

Weekly batch — connection requests + 1:1 DM drafts targeted at salon owners and managers in Istanbul (later Ankara, Izmir). Feeds the sales-bd pipeline.

When to Use

• Friday cycle
• A salon-targeted post just hit the feed (capitalize on reach)

Process

1. Pull the current lead list from agents/sales-bd/outputs/<latest>_pipeline.md. Filter for linkedin_url present and status: not_contacted.
2. Cap batch at 15 connection requests + 5 DM drafts / week (LinkedIn safe limit + reply quality > volume).
3. Per lead:
   • Verify role on LinkedIn (owner, manager, head stylist OK; staff stylist skip — wrong buyer).
   • Draft a 1-sentence connection note (Turkish, no marketing).
   • For top-5 prospects, draft a longer first DM. Reference one specific thing about their salon (location, services, post).
4. Save to outputs/YYYY-MM-DD_salon_outreach.md.
5. After Emir sends + receives replies, push reply log back to sales-bd via journal entry.

Templates

Connection note (TR, 1 line)

Merhaba <isim>, Istanbul'da salon sahipleri icin glossgo'yu kuruyoruz — sektorden insanlarla iletisimde kalmak isterim.

First DM (TR, 4-6 sentences)

Merhaba <isim>,

<Salon> hakkinda <bir spesifik sey>'yi gordum, dikkat cekti.

glossgo'da Istanbul'daki salonlar icin <bir somut yarar — randevu doldurma, fiyat seffafligi, AI oneri>. <Sosyal kanit ya da metrik>.

15 dakika sohbet edebilir miyiz? Sizin icin uygun mu?

Tesekkurler,
Emir

Quality Bar

• No mass-blast template — every DM has one specific detail about that salon
• No mention of competitor names
• 15 connect / 5 DM per week max
• All replies logged back via journal — no reply log = sales-bd loses the lead
• KVKK note: do not store personal data outside the agents/sales-bd/data/ pipeline; the outreach file holds public-LinkedIn info only