Skip to content

Commit 8fa3d56

Browse files
NeilJo-GYNeilJo-GY
committed
fix(brand-persona-skill): add closing --- to frontmatter for skills CLI compatibility
Made-with: Cursor
1 parent 31293ec commit 8fa3d56

1 file changed

Lines changed: 17 additions & 15 deletions

File tree

‎skills/brand-persona-skill/SKILL.md‎

Lines changed: 17 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -132,16 +132,16 @@ List every service the agent can handle without human involvement. Think in two
132132
For each service declared above, the implementation method is **transparent to this skill** — the brand chooses based on what they have:
133133

134134

135-
| Implementation | When to use | Example |
136-
| ------------------ | ---------------------------------------------------------------------------- | -------------------------------------------------------------------------------------- |
137-
| Knowledge response | Information queries, no system integration | Business hours, product descriptions, policies |
138-
| Local script | Specific business operations | Queue number generation, appointment booking |
139-
| MCP tool | Has own service endpoint | Order lookup, inventory check |
140-
| A2A protocol | Agent-to-agent collaboration | Cross-system business flows |
141-
| Webhook / API | Has existing ERP / CRM / payment system | Order management, customer data |
142-
| Human handoff | High-risk or complex situations | Complaints, contracts, disputes |
135+
| Implementation | When to use | Example |
136+
| ------------------ | ---------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------- |
137+
| Knowledge response | Information queries, no system integration | Business hours, product descriptions, policies |
138+
| Local script | Specific business operations | Queue number generation, appointment booking |
139+
| MCP tool | Has own service endpoint | Order lookup, inventory check |
140+
| A2A protocol | Agent-to-agent collaboration | Cross-system business flows |
141+
| Webhook / API | Has existing ERP / CRM / payment system | Order management, customer data |
142+
| Human handoff | High-risk or complex situations | Complaints, contracts, disputes |
143143
| **A2A delegate** | **Operation belongs to a third-party platform that has its own brand agent** | **F&B: queue via Meituan agent; Hotel: booking via Ctrip agent; Fitness: class sign-up via booking platform agent** |
144-
| Mixed | Most real businesses | Auto-answer queries + escalate transactions |
144+
| Mixed | Most real businesses | Auto-answer queries + escalate transactions |
145145

146146

147147
Record the implementation method in the skill's `description` field.
@@ -151,9 +151,9 @@ Record the implementation method in the skill's `description` field.
151151
1. **Third-party agent address** — Ask: "Does [third-party platform] have a brand agent on ACN? If yes, provide its ACN slug or agent-card URL. If not, record as `tbd`."
152152
2. **Routing parameters** — Ask: "Does [third-party platform] need any identifiers to locate your specific business? For example, a store ID, merchant ID, property code, or doctor ID on their platform." Record these parameters (e.g. `shop_id: 4211342` for a restaurant branch; `hotel_id: bj-sanlitun-001` for a hotel property; `clinic_id: 88` + `doctor_id: 204` for a clinic) — they will be written into the trigger mapping table in Step 4c.
153153
3. **Client-side capability** — Ask: "Is there a skill the customer's agent could install to handle this operation directly using the parameters above? For example, `meituan-queue` for Meituan queue operations, `ctrip-booking` for Ctrip hotel reservations, `wechat-health-booking` for healthcare appointments." This enables a three-tier execution model written into the service contract:
154-
- **Tier 1** (preferred): customer agent has `capability_needed` skill installed → execute directly using the routing parameters provided by this brand agent
155-
- **Tier 2** (when available): third-party brand agent is on ACN → A2A delegate
156-
- **Tier 3** (fallback): neither available → human handoff or platform link
154+
- **Tier 1** (preferred): customer agent has `capability_needed` skill installed → execute directly using the routing parameters provided by this brand agent
155+
- **Tier 2** (when available): third-party brand agent is on ACN → A2A delegate
156+
- **Tier 3** (fallback): neither available → human handoff or platform link
157157

158158
Record all three fields. They will be written into both the trigger mapping table (Step 4c) and the SERVICE-CONTRACT routing table (Step 4d).
159159

@@ -169,9 +169,11 @@ List hard limits and escalation triggers:
169169

170170
Summarise all A2A delegate entries collected above into a routing table for confirmation before proceeding. For each delegated service, verify the three fields collected in Question 2 are complete:
171171

172-
| Service | Routing parameters | Client-side capability | Third-party agent ACN | Fallback |
173-
|---|---|---|---|---|
174-
| {service collected in Q2} | {params collected in Q2} | {capability collected in Q2} | {ACN slug or "tbd"} | {platform link or human channel} |
172+
173+
| Service | Routing parameters | Client-side capability | Third-party agent ACN | Fallback |
174+
| ------------------------- | ------------------------ | ---------------------------- | --------------------- | -------------------------------- |
175+
| {service collected in Q2} | {params collected in Q2} | {capability collected in Q2} | {ACN slug or "tbd"} | {platform link or human channel} |
176+
175177

176178
Ask the user to confirm or correct any row. Once confirmed, this table is written verbatim into `SERVICE-CONTRACT.md` in Phase 4.
177179

0 commit comments

Comments
 (0)