agentleFS
Nomanriaz786Nomanriaz786/claude-consulting-team/skills/client-kickoff/SKILL.md

client-kickoff

Skill1 starsChanged 23 days agoMITView on GitHub

Plans a client kickoff when contracted work must begin with shared expectations, roles and immediate actions.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    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:

    Use after signature and before substantive delivery work starts.

    line 9

≈ “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

Client Kickoff

When to use it

Use after signature and before substantive delivery work starts.

What Claude needs

  • client-context.md for business background
  • Final statement of work and workplan
  • Attendees, roles and stakeholder map
  • Known risks, dependencies and required access

Method

  1. Translate contract commitments into a concise shared engagement charter.
  2. Build an agenda covering outcomes, scope, approach, roles and ways of working.
  3. Confirm governance, decision rights, escalation and change control.
  4. Validate milestones, acceptance criteria, client inputs and access dates.
  5. Facilitate a pre-mortem to surface delivery and relationship risks.
  6. Capture decisions, actions, owners and dates in a kickoff record.

Output format

Provide a timed agenda, engagement charter, decision-rights table, risk prompts and action register.

Quality checks

  • Matches the signed scope and latest workplan
  • Gives each action one accountable owner
  • Surfaces unresolved issues without silently changing terms

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.