agentleFS
salvo8519salvo8519/fairmark/.claude/skills/onboarding/SKILL.md

onboarding

Skill1 starsChanged 2 days agoApache-2.0View on GitHub

Onboard a new contributor, forker or evaluator in their own language — guided tour of Fairmark's purpose, architecture, workflow and first tasks, with on-the-fly translation of any document. Use when someone new asks to understand, explore or start contributing to the project, in any language.

106 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use paywalls, popups and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • CesarjoquinSkill

    paywalls

    When the user wants to create or optimize in-app paywalls, upgrade screens, upsell modals, or feature gates. Also use when the user mentions "paywall," "upgrade screen," "upgrade modal," "upsell," "feature gate," "convert free to paid," "freemium conversion," "trial expiration screen," "limit reached screen," "plan upgrade prompt," "in-app pricing," "free users won't upgrade," "trial to paid conversion," or "how do I get users to pay." Use this for any in-product moment where you're asking users to upgrade. Distinct from public pricing pages (see cro) — this focuses on in-product upgrade moments where the user has already experienced value. For pricing decisions, see pricing.

    Also in 19 projects that use this

  • CesarjoquinSkill

    popups

    When the user wants to create or optimize popups, modals, overlays, slide-ins, or banners for conversion purposes. Also use when the user mentions "exit intent," "popup conversions," "modal optimization," "lead capture popup," "email popup," "announcement banner," "overlay," "collect emails with a popup," "exit popup," "scroll trigger," "sticky bar," or "notification bar." Use this for any overlay or interrupt-style conversion element. For forms outside of popups, see cro. For general page conversion optimization, see cro.

    Also in 18 projects that use this

  • coreyhaines31Skill

    marketing-council

    When the user wants several expert takes on a marketing decision, or asks what a famous marketer would say about it: a simulated board (Seth Godin, David Ogilvy, April Dunford, Byron Sharp, and more), each grounded in their documented frameworks, where they disagree, and a recommendation. To execute, hand off to the relevant skill.

    Also in 13 projects that use this

  • roerohanSkill

    prospecting

    When the user wants to find, qualify, and build a list of prospects to reach out to — across B2B SaaS, general B2B, or local small businesses. Also use when the user mentions "prospecting," "build a prospect list," "find prospects," "find leads," "lead gen list," "find SaaS companies that," "find B2B companies," "find local businesses," "ICP-fit accounts," "who should we go after," "outbound list," "target account list," "find clients near me," "businesses without websites," "prospect research," "qualified leads," "find my first customers," "early adopters," "design partners," "beta users," or "who has this problem." Use this for the list-building and qualification phase. For writing the outbound copy after the list is built, see cold-email. For deep competitive research on specific accounts, see competitor-profiling.

    Also in 16 projects that use this

  • roerohanSkill

    emails

    When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "re-engagement emails," "email automation," "lifecycle emails," "trigger-based emails," "email funnel," "email workflow," "what emails should I send," "welcome series," or "email cadence." Use this for any multi-email automated flow. For cold outreach emails, see cold-email. For in-app onboarding, see onboarding.

    Also in 18 projects that use this

  • +7 more from Cesarjoquin

The file

Files
SKILL.md
<!-- Generated from .agents/skills/onboarding/SKILL.md by scripts/sync_agents.py. Edit the source, not this file. -->

Detect the reader's language from their messages (ask if unclear). Everything you say is in that language; the files you read stay as they are.

  1. Purpose — summarise README.md and docs/en/project/vision.md: what Fairmark does, for whom, what makes it different.
  2. Principles — explain specs/constitution.md in plain words, with one example each.
  3. Architecture — walk through docs/en/concepts/architecture.md and the repository map in AGENTS.md; open one method end to end (crates/fairmark-core/src/dcf.rs, its golden cases, its documentation page) to make it concrete.
  4. How work is done — spec-driven development (specs/README.md), agents and skills (.agents/README.md), the quality gate (uv run just check), sprints (sprints/README.md).
  5. Set up — uv sync --all-extras --all-groups, uv run just check, and make sure it is green before anything else.
  6. First contribution — list open good first issue issues (gh issue list --label "good first issue") and suggest two that fit the person's skills (developer, valuation professional, translator).
  7. Reading in their language — on request, translate any document on the fly in the conversation. Do not commit translations: maintained languages are decided by the maintainers. If the person wants to maintain a new language, explain the process: i18n/<lang>.yaml, a glossary, docs/<lang>/, README.<lang>.md, then a PR discussed with the maintainers first.

Contributions themselves (code, commits, issues, PRs) are in English, as stated in CONTRIBUTING.md. No icons or emoji.

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.