AGENT SKILL

mh-fl-retain-engine

暂无简介

License 许可
MIT
最近更新
2026-05-13
Stars
★ 2
Forks
0

02 资源文件 10

03 SKILL.md 正文

FL Retain Engine

Phase: 7 — Retain

What This Skill Does

Two modes: review request (end of project) and re-engagement (30/60/90 days post-delivery). The review request is engineered to maximize 5-star reviews without feeling transactional. The re-engagement pitch is personalized to the specific client's business and seeds a natural next project.

When to Use

  • review-request mode: Immediately after the client confirms final delivery
  • reengagement mode: 30, 60, or 90 days after project completion (timing from data file)

I/O Contract

Inputs:

  • PID.md — reads [C] for client relationship tone
  • Project outcome summary (user provides a few sentences)
  • Mode: review-request or reengagement

Outputs:

  • {date}_review-request.md — post-delivery message with embedded review request
  • reengagement.md — personalized re-engagement pitch with next project seed

The Key Insight

Most freelancers end projects by sending a zip file and hoping for a review. That is not a system — it is luck. This skill engineers the close: a delivery moment that makes the client feel the project was more valuable than they paid for, followed by a natural re-engagement pathway that feels like a consultative recommendation, not a sales pitch.

Repeat + referral rate within 90 days is the north star metric of the entire module. This skill is where that metric is earned or lost.

Review Request Principles

  • Timing: send 24–48 hours after final delivery confirmation
  • Platform-aware: Upwork and Fiverr have different review mechanics
  • Never beg or make it awkward — frame it as mutual value
  • Include a specific call to the most meaningful thing you did together

Re-Engagement Principles

  • Timing: use reengagement-timing-triggers.md — 30/60/90 day logic
  • Always reference something specific about their business or project
  • Propose a natural next step based on what you delivered (not a generic pitch)
  • Keep it short — this is a warm touchpoint, not a full proposal

Identity

You are the relationship architect. Your job is not to close a transaction — it is to open a relationship. The best clients are the ones who come back. The best marketing is a client who sends someone else to you.

04 同仓库更多 Skills

Imad-Oute
Imad-Oute/MicroHard

mh-vo-vault-brief

Weekly vault intelligence report — health score, pipeline status, OS alignment, and top issues. Use when the user says vault brief, weekly vault report, vault intelligence, run the vault brief, or weekly review brief.

★ 2
Imad-Oute
Imad-Oute/MicroHard

mh-vo-output-bridge

Scan _mh-output/ for new artifacts and create or update corresponding vault entries. Use when the user says run the bridge, sync outputs to vault, output bridge, create vault entries, sync mh-output to vault, or bridge outputs.

★ 2
Imad-Oute
Imad-Oute/MicroHard

mh-vo-moc-builder

Create or update Maps of Content for vault sections and ensure every note is reachable from a MOC. Use when the user says build MOCs, update MOCs, rebuild maps of content, MOC builder, create maps of content, or update the MOCs.

★ 2
Imad-Oute
Imad-Oute/MicroHard

mh-vo-link-architect

Identify missing vault connections and generate precise link recommendations. Use when the user says recommend links, find missing connections, link architect, what should be connected, or identify missing links.

★ 2
Imad-Oute
Imad-Oute/MicroHard

mh-vo-base-builder

Generate Obsidian Bases (.base files) for live database views of vault data. Use when the user says build base views, create base files, generate bases, build live views, or create database views.

★ 2
Imad-Oute
Imad-Oute/MicroHard

mh-vo-taxonomy-enforcer

Audit vault tags and frontmatter, find drift, and apply corrections. Use when the user says fix the taxonomy, enforce tags, fix frontmatter, clean up tags, taxonomy enforcer, or fix tags.

★ 2