agentleFS
Duckz289Duckz289/Pipeline-to-proposal-Plugin-STANDARD/skills/getting-started/SKILL.md

getting-started

Skill2 starsChanged 4 months agoMITView on GitHub

Introduces the plugin with copy-paste examples, for new users or vague requests. Triggered by "plugin này làm được gì", "hướng dẫn", "bắt đầu sao", "dùng thế nào", "chào", "hello", "help", "what can you do", or any sales request with no clear output.

32 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

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

  • 0

    Common

    Most of the 32 edited versions we read keep these.

  • 2

    Distinctive

    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:

    Use when the user does not know what to type, or the request is too general to guess which artifact they need.

    line 11
  2. Distinctive:

    If the user already said what they sell anywhere in this conversation, use that — real product, real rough price if known.

    line 25

“Common” is measured: kept by at least 6 in 10 of the 32 edited versions of this file we could read. “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

Getting started

Use when the user does not know what to type, or the request is too general to guess which artifact they need.

Give copy-paste examples, not an abstract menu. A newcomer does not know what "research" or "pipeline" means in this context.

Standard response

Return this structure, in the user's language.

The middle example must never default to software. A first-time user reads it as "who this plugin is for" — if it always says "phần mềm quản lý kho", anyone selling something else quietly concludes this is a dev tool and leaves. Two rules, in order:

  1. If the user already said what they sell anywhere in this conversation, use that — real product, real rough price if known.
  2. Otherwise, pick one non-software example and vary it between conversations rather than defaulting to the same one every time — rotate through a physical good, a service, and a professional service, not three variations of software:

    • "mình bán dịch vụ vệ sinh văn phòng, từ 3 triệu/tháng"
    • "mình bán vật liệu xây dựng, báo giá theo đơn hàng"
    • "mình bán dịch vụ kế toán thuê ngoài, từ 5 triệu/tháng"
    • "mình bán máy móc công nghiệp cho nhà xưởng"

Vietnamese:

Mình giúp bạn ba việc. Copy một dòng dưới đây rồi sửa cho đúng khách của bạn:

**Tìm hiểu một công ty trước khi liên hệ**
    Tìm hiểu công ty ABC giúp mình

**Viết email chào hàng hoặc follow-up**
    Viết email cho ABC, mình bán dịch vụ vệ sinh văn phòng từ 3 triệu/tháng

**Khách im lặng, không biết làm gì tiếp**
    Gửi proposal cho ABC 5 ngày rồi chưa thấy trả lời

Sau khi gửi cho khách, cứ nhắn mình kết quả — "khách trả lời rồi" hoặc "chưa thấy hồi âm" —
mình sẽ nhớ giúp deal đó đang tới đâu.

(Swap the second example's product/price for one of the rotation above, or the user's own stated offer, each time this screen is shown — do not let it ossify into a fixed script.)

English:

I can help with three things. Copy a line below and change it to fit your prospect:

**Look into a company before reaching out**
    Tell me about ABC Logistics

**Write a cold email or a follow-up**
    Write an email to ABC, I sell office cleaning services from $150/month

**They've gone quiet and you're not sure what to do**
    Sent ABC a proposal 5 days ago, no response

After you send something, just tell me what happened — "they replied" or "still nothing" —
and I'll keep track of where each deal stands.

If they ask something specific

"Where is my data stored?" → Give the real path (see ${CLAUDE_PLUGIN_ROOT}/policies/state-management.md), and be clear: deal memory stays on their machine and the plugin author receives nothing, but chat content still goes to Claude like any other conversation.

"Does it send emails for me?" → No. It drafts, they send. It does not write to a CRM either.

"Do I need to install anything else?" → No. No server, no database, no API key.

"I sell [X] — will this work?" → Yes if it is B2B, selling to companies or organisations. Less useful for consumer retail.

Routing

They sayGo to
research, "tell me about this company"${CLAUDE_PLUGIN_ROOT}/skills/research-prospect/SKILL.md
email, follow-up, message${CLAUDE_PLUGIN_ROOT}/skills/draft-outreach-email/SKILL.md
proposal, quote${CLAUDE_PLUGIN_ROOT}/skills/draft-proposal/SKILL.md
stuck deal, no response, what next${CLAUDE_PLUGIN_ROOT}/skills/suggest-next-step/SKILL.md
several things at once${CLAUDE_PLUGIN_ROOT}/skills/run-pipeline/SKILL.md
remember my offer${CLAUDE_PLUGIN_ROOT}/skills/setup-product-context/SKILL.md

Never show this screen when the user already made a clear request. It is only for when they are stuck.

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.