exp-invite

Invite a qualified customer into the experience group when they want to understand the product form further after seeing demo materials. The invite is sent as an awada control message, and the customer status is updated to exp_invited to prevent duplicate invitations.

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill body is a tight, actionable, single-purpose workflow backed by a real executable script, with clear sequencing, validation, and a clean one-level bundle structure that fully aligns with the documented behavior.

Dimension	Reasoning	Score
Conciseness	The body is lean and well-sectioned (purpose, identifier rules, behavior rules, status updates, message format, return conventions) with no padding of concepts Claude already knows.	3 / 3
Actionability	Provides fully executable bash commands with exact flags, the literal control-message format, and a real backing script (scripts/invite.sh) that implements the documented behavior — copy-paste ready.	3 / 3
Workflow Clarity	The single-task workflow is clearly sequenced (extract identifiers, check status, block or force, conditionally update status, emit control message) with documented validation and an explicit error path (ALREADY_INVITED / non-zero exit).	3 / 3
Progressive Disclosure	Content is organized into clear sections with a single one-level-deep bundle reference (scripts/invite.sh) that genuinely exists and matches the documented commands; no nested references.	3 / 3
	Total	12 / 12 Passed

Description

75%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description clearly conveys a specific internal workflow with an explicit when-trigger and strong distinctiveness, but relies on domain jargon rather than natural user phrasing and only partially enumerates its actions.

Suggestions

Add natural-language trigger terms a user might actually say (e.g. 'invite to experience group', 're-invite', 'demo follow-up') alongside the internal terminology.

Consider listing the concrete actions more comprehensively (send invite, update business_status, block duplicates, force re-invite) to lift specificity to the top anchor.

Dimension	Reasoning	Score
Specificity	Names the domain (experience-group invite) and concrete actions ('sent as an awada control message', 'updated to exp_invited'), but does not enumerate a comprehensive list of multiple actions like the score-3 anchor.	2 / 3
Completeness	States both what it does (invite via awada control message, update status to exp_invited) and when to use it with an explicit trigger clause, answering both halves.	3 / 3
Trigger Term Quality	Contains an explicit situational trigger ('when they want to understand the product form further after seeing demo materials'), but the terms are internal jargon rather than natural keywords a user would say.	2 / 3
Distinctiveness Conflict Risk	Targets a narrow, internally-specific niche (awada control message, exp_invited status) with distinct triggers, making conflict with other skills unlikely.	3 / 3
	Total	10 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: TeamWiseFlow/xiaobei
Path: crews/sales-cs/skills/exp-invite/SKILL.md
Commit: bcef823

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.