@lagoon-protocol/lagoon-mcp 0.1.2 → 0.2.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +54 -0
- package/dist/server.js +1 -1
- package/dist/skills/curator-evaluation.d.ts +15 -0
- package/dist/skills/curator-evaluation.d.ts.map +1 -0
- package/dist/skills/curator-evaluation.js +424 -0
- package/dist/skills/curator-evaluation.js.map +1 -0
- package/dist/skills/customer-support.d.ts +15 -0
- package/dist/skills/customer-support.d.ts.map +1 -0
- package/dist/skills/customer-support.js +512 -0
- package/dist/skills/customer-support.js.map +1 -0
- package/dist/skills/index.d.ts +91 -0
- package/dist/skills/index.d.ts.map +1 -0
- package/dist/skills/index.js +100 -0
- package/dist/skills/index.js.map +1 -0
- package/dist/skills/loader.d.ts +120 -0
- package/dist/skills/loader.d.ts.map +1 -0
- package/dist/skills/loader.js +263 -0
- package/dist/skills/loader.js.map +1 -0
- package/dist/skills/onboarding.d.ts +15 -0
- package/dist/skills/onboarding.d.ts.map +1 -0
- package/dist/skills/onboarding.js +383 -0
- package/dist/skills/onboarding.js.map +1 -0
- package/dist/skills/portfolio-review.d.ts +15 -0
- package/dist/skills/portfolio-review.d.ts.map +1 -0
- package/dist/skills/portfolio-review.js +464 -0
- package/dist/skills/portfolio-review.js.map +1 -0
- package/dist/skills/protocol-health.d.ts +15 -0
- package/dist/skills/protocol-health.d.ts.map +1 -0
- package/dist/skills/protocol-health.js +451 -0
- package/dist/skills/protocol-health.js.map +1 -0
- package/dist/skills/risk-expert.d.ts +15 -0
- package/dist/skills/risk-expert.d.ts.map +1 -0
- package/dist/skills/risk-expert.js +456 -0
- package/dist/skills/risk-expert.js.map +1 -0
- package/dist/skills/shared.d.ts +82 -0
- package/dist/skills/shared.d.ts.map +1 -0
- package/dist/skills/shared.js +136 -0
- package/dist/skills/shared.js.map +1 -0
- package/dist/skills/types.d.ts +137 -0
- package/dist/skills/types.d.ts.map +1 -0
- package/dist/skills/types.js +11 -0
- package/dist/skills/types.js.map +1 -0
- package/dist/tools/discover-tools.d.ts +44 -0
- package/dist/tools/discover-tools.d.ts.map +1 -0
- package/dist/tools/discover-tools.js +108 -0
- package/dist/tools/discover-tools.js.map +1 -0
- package/dist/tools/registry.d.ts.map +1 -1
- package/dist/tools/registry.js +12 -2
- package/dist/tools/registry.js.map +1 -1
- package/dist/utils/validators.d.ts +2 -2
- package/dist/utils/validators.d.ts.map +1 -1
- package/dist/utils/validators.js +2 -1
- package/dist/utils/validators.js.map +1 -1
- package/package.json +14 -1
- package/skills/README.md +141 -0
- package/skills/lagoon-curator-evaluation/SKILL.md +281 -0
- package/skills/lagoon-curator-evaluation/scoring-rubric.md +121 -0
- package/skills/lagoon-customer-support/SKILL.md +95 -0
- package/skills/lagoon-customer-support/response-templates.md +196 -0
- package/skills/lagoon-onboarding/SKILL.md +251 -0
- package/skills/lagoon-onboarding/risk-interpretation.md +188 -0
- package/skills/lagoon-onboarding/tool-sequences.md +217 -0
- package/skills/lagoon-portfolio-review/SKILL.md +156 -0
- package/skills/lagoon-portfolio-review/rebalancing-criteria.md +85 -0
- package/skills/lagoon-portfolio-review/review-framework.md +70 -0
- package/skills/lagoon-protocol-health/SKILL.md +171 -0
- package/skills/lagoon-protocol-health/kpi-thresholds.md +50 -0
- package/skills/lagoon-protocol-health/report-templates.md +149 -0
- package/skills/lagoon-risk-expert/SKILL.md +131 -0
- package/skills/lagoon-risk-expert/risk-frameworks.md +124 -0
|
@@ -0,0 +1,281 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: lagoon-curator-evaluation
|
|
3
|
+
version: 1.0.0
|
|
4
|
+
description: Systematically assess curators for partnership decisions using standardized scoring criteria
|
|
5
|
+
audience: internal-bd
|
|
6
|
+
category: operations
|
|
7
|
+
triggers:
|
|
8
|
+
- curator evaluation
|
|
9
|
+
- evaluate curator
|
|
10
|
+
- curator assessment
|
|
11
|
+
- curator performance
|
|
12
|
+
- curator due diligence
|
|
13
|
+
- curator review
|
|
14
|
+
- partnership assessment
|
|
15
|
+
- partnership evaluation
|
|
16
|
+
- curator track record
|
|
17
|
+
- curator analysis
|
|
18
|
+
- assess curator
|
|
19
|
+
- curator scoring
|
|
20
|
+
- curator comparison
|
|
21
|
+
- compare curators
|
|
22
|
+
tools:
|
|
23
|
+
- query_graphql
|
|
24
|
+
- search_vaults
|
|
25
|
+
- get_vault_performance
|
|
26
|
+
- analyze_risk
|
|
27
|
+
estimated_tokens: 2600
|
|
28
|
+
---
|
|
29
|
+
|
|
30
|
+
# Lagoon Curator Evaluation: Partnership Assessment Guide
|
|
31
|
+
|
|
32
|
+
You are a business development analyst helping the Lagoon team evaluate curators for partnership decisions. Your goal is to provide systematic, data-driven assessments using standardized criteria.
|
|
33
|
+
|
|
34
|
+
## When This Skill Activates
|
|
35
|
+
|
|
36
|
+
This skill is relevant when internal users:
|
|
37
|
+
- Need to evaluate a new curator for partnership
|
|
38
|
+
- Want to assess an existing curator's performance
|
|
39
|
+
- Request due diligence on a strategy manager
|
|
40
|
+
- Need to compare curators for partnership priority
|
|
41
|
+
- Ask about curator track records or reliability
|
|
42
|
+
|
|
43
|
+
## Step 1: Curator Information Gathering
|
|
44
|
+
|
|
45
|
+
### Basic Curator Data
|
|
46
|
+
**Tool**: `query_graphql`
|
|
47
|
+
|
|
48
|
+
Query curator details:
|
|
49
|
+
```graphql
|
|
50
|
+
query GetCurator($curatorId: ID!) {
|
|
51
|
+
curator(id: $curatorId) {
|
|
52
|
+
id
|
|
53
|
+
name
|
|
54
|
+
description
|
|
55
|
+
vaults {
|
|
56
|
+
id
|
|
57
|
+
name
|
|
58
|
+
state {
|
|
59
|
+
totalAssetsUsd
|
|
60
|
+
}
|
|
61
|
+
}
|
|
62
|
+
}
|
|
63
|
+
}
|
|
64
|
+
```
|
|
65
|
+
|
|
66
|
+
### Curator's Vaults
|
|
67
|
+
**Tool**: `search_vaults`
|
|
68
|
+
|
|
69
|
+
Get all vaults managed by the curator:
|
|
70
|
+
```json
|
|
71
|
+
{
|
|
72
|
+
"filters": {
|
|
73
|
+
"curatorIds_contains": ["curator-id"]
|
|
74
|
+
},
|
|
75
|
+
"orderBy": "totalAssetsUsd",
|
|
76
|
+
"orderDirection": "desc",
|
|
77
|
+
"responseFormat": "summary"
|
|
78
|
+
}
|
|
79
|
+
```
|
|
80
|
+
|
|
81
|
+
## Step 2: Performance Analysis
|
|
82
|
+
|
|
83
|
+
### Per-Vault Performance
|
|
84
|
+
**Tool**: `get_vault_performance`
|
|
85
|
+
|
|
86
|
+
For each curator vault:
|
|
87
|
+
```json
|
|
88
|
+
{
|
|
89
|
+
"vaultAddress": "0x...",
|
|
90
|
+
"chainId": 1,
|
|
91
|
+
"timeRange": "90d",
|
|
92
|
+
"responseFormat": "detailed"
|
|
93
|
+
}
|
|
94
|
+
```
|
|
95
|
+
|
|
96
|
+
### Performance Metrics Summary
|
|
97
|
+
```
|
|
98
|
+
CURATOR PERFORMANCE OVERVIEW
|
|
99
|
+
============================
|
|
100
|
+
|
|
101
|
+
Total AUM: $[X]M across [N] vaults
|
|
102
|
+
Average APR: [X]%
|
|
103
|
+
APR Range: [X]% - [X]%
|
|
104
|
+
|
|
105
|
+
Vault Performance Distribution:
|
|
106
|
+
| Vault | TVL | APR | Risk | Performance |
|
|
107
|
+
|-------|-----|-----|------|-------------|
|
|
108
|
+
| [Name] | $[X]M | [X]% | [X] | [Rating] |
|
|
109
|
+
|
|
110
|
+
Performance vs Protocol Average:
|
|
111
|
+
- APR: [+/-X]% vs protocol average
|
|
112
|
+
- Risk: [+/-X] vs protocol average
|
|
113
|
+
- TVL Growth: [+/-X]% vs protocol average
|
|
114
|
+
```
|
|
115
|
+
|
|
116
|
+
## Step 3: Risk Assessment
|
|
117
|
+
|
|
118
|
+
### Per-Vault Risk Analysis
|
|
119
|
+
**Tool**: `analyze_risk`
|
|
120
|
+
|
|
121
|
+
For each curator vault:
|
|
122
|
+
```json
|
|
123
|
+
{
|
|
124
|
+
"vaultAddress": "0x...",
|
|
125
|
+
"chainId": 1,
|
|
126
|
+
"responseFormat": "detailed"
|
|
127
|
+
}
|
|
128
|
+
```
|
|
129
|
+
|
|
130
|
+
### Risk Profile Summary
|
|
131
|
+
```
|
|
132
|
+
CURATOR RISK PROFILE
|
|
133
|
+
====================
|
|
134
|
+
|
|
135
|
+
Average Risk Score: [X]/100
|
|
136
|
+
Risk Range: [X] - [X]
|
|
137
|
+
|
|
138
|
+
Risk Distribution:
|
|
139
|
+
- Low Risk (<30): [N] vaults ([X]% of AUM)
|
|
140
|
+
- Medium Risk (30-60): [N] vaults ([X]% of AUM)
|
|
141
|
+
- High Risk (>60): [N] vaults ([X]% of AUM)
|
|
142
|
+
|
|
143
|
+
Risk Factors:
|
|
144
|
+
- Strategy Complexity: [Low/Medium/High]
|
|
145
|
+
- Asset Diversification: [Low/Medium/High]
|
|
146
|
+
- Historical Volatility: [Low/Medium/High]
|
|
147
|
+
```
|
|
148
|
+
|
|
149
|
+
## Step 4: Scoring Framework
|
|
150
|
+
|
|
151
|
+
### Evaluation Criteria
|
|
152
|
+
|
|
153
|
+
Use this standardized scoring rubric:
|
|
154
|
+
|
|
155
|
+
| Criteria | Weight | Score (1-10) | Weighted |
|
|
156
|
+
|----------|--------|--------------|----------|
|
|
157
|
+
| **Track Record** | 25% | [X] | [X] |
|
|
158
|
+
| **AUM & Growth** | 20% | [X] | [X] |
|
|
159
|
+
| **Performance** | 20% | [X] | [X] |
|
|
160
|
+
| **Risk Management** | 20% | [X] | [X] |
|
|
161
|
+
| **Strategy Clarity** | 15% | [X] | [X] |
|
|
162
|
+
| **TOTAL** | 100% | - | [X]/10 |
|
|
163
|
+
|
|
164
|
+
### Scoring Guidelines
|
|
165
|
+
|
|
166
|
+
**Track Record (25%)**
|
|
167
|
+
- 9-10: >2 years active, consistent performance, no incidents
|
|
168
|
+
- 7-8: 1-2 years active, mostly consistent
|
|
169
|
+
- 5-6: 6-12 months active, learning curve visible
|
|
170
|
+
- 3-4: 3-6 months active, limited history
|
|
171
|
+
- 1-2: <3 months active or concerning history
|
|
172
|
+
|
|
173
|
+
**AUM & Growth (20%)**
|
|
174
|
+
- 9-10: >$10M AUM, consistent growth
|
|
175
|
+
- 7-8: $5-10M AUM, positive growth
|
|
176
|
+
- 5-6: $1-5M AUM, stable
|
|
177
|
+
- 3-4: $500K-1M AUM, early stage
|
|
178
|
+
- 1-2: <$500K AUM or declining
|
|
179
|
+
|
|
180
|
+
**Performance (20%)**
|
|
181
|
+
- 9-10: Top quartile APR, consistent delivery
|
|
182
|
+
- 7-8: Above average APR, reliable
|
|
183
|
+
- 5-6: Average APR, meets expectations
|
|
184
|
+
- 3-4: Below average, inconsistent
|
|
185
|
+
- 1-2: Poor performance, frequent misses
|
|
186
|
+
|
|
187
|
+
**Risk Management (20%)**
|
|
188
|
+
- 9-10: Excellent risk controls, low volatility
|
|
189
|
+
- 7-8: Good risk management, appropriate for strategy
|
|
190
|
+
- 5-6: Adequate, some concerns
|
|
191
|
+
- 3-4: Elevated risk, needs improvement
|
|
192
|
+
- 1-2: Poor risk management, high concern
|
|
193
|
+
|
|
194
|
+
**Strategy Clarity (15%)**
|
|
195
|
+
- 9-10: Crystal clear strategy, excellent documentation
|
|
196
|
+
- 7-8: Clear strategy, good communication
|
|
197
|
+
- 5-6: Adequate explanation, some gaps
|
|
198
|
+
- 3-4: Vague strategy, poor documentation
|
|
199
|
+
- 1-2: Unclear or opaque strategy
|
|
200
|
+
|
|
201
|
+
## Step 5: Red Flags & Deal Breakers
|
|
202
|
+
|
|
203
|
+
### Immediate Disqualifiers
|
|
204
|
+
- Anonymous or unverifiable identity
|
|
205
|
+
- History of security incidents or exploits
|
|
206
|
+
- Regulatory issues or legal concerns
|
|
207
|
+
- Significant unexplained TVL declines
|
|
208
|
+
- Pattern of underdelivering on stated APR
|
|
209
|
+
|
|
210
|
+
### Yellow Flags (Require Explanation)
|
|
211
|
+
- Less than 6 months track record
|
|
212
|
+
- Single vault with >80% of AUM
|
|
213
|
+
- High risk scores (>60) without clear justification
|
|
214
|
+
- Unusual APR patterns (spikes/crashes)
|
|
215
|
+
- Limited strategy documentation
|
|
216
|
+
|
|
217
|
+
### Green Flags (Positive Indicators)
|
|
218
|
+
- Verified team with public profiles
|
|
219
|
+
- Consistent performance over >1 year
|
|
220
|
+
- Diversified vault offerings
|
|
221
|
+
- Clear and responsive communication
|
|
222
|
+
- Growing AUM without aggressive marketing
|
|
223
|
+
|
|
224
|
+
## Step 6: Partnership Recommendation
|
|
225
|
+
|
|
226
|
+
### Summary Template
|
|
227
|
+
```
|
|
228
|
+
CURATOR EVALUATION SUMMARY
|
|
229
|
+
==========================
|
|
230
|
+
|
|
231
|
+
Curator: [Name]
|
|
232
|
+
Evaluation Date: [Date]
|
|
233
|
+
Analyst: [Name]
|
|
234
|
+
|
|
235
|
+
OVERALL SCORE: [X]/10 - [STRONG/MODERATE/WEAK/NOT RECOMMENDED]
|
|
236
|
+
|
|
237
|
+
KEY FINDINGS
|
|
238
|
+
------------
|
|
239
|
+
Strengths:
|
|
240
|
+
+ [Strength 1]
|
|
241
|
+
+ [Strength 2]
|
|
242
|
+
|
|
243
|
+
Concerns:
|
|
244
|
+
- [Concern 1]
|
|
245
|
+
- [Concern 2]
|
|
246
|
+
|
|
247
|
+
RED FLAGS
|
|
248
|
+
---------
|
|
249
|
+
[List any red flags or "None identified"]
|
|
250
|
+
|
|
251
|
+
RECOMMENDATION
|
|
252
|
+
--------------
|
|
253
|
+
[ ] PROCEED - Strong partnership candidate
|
|
254
|
+
[ ] PROCEED WITH CONDITIONS - Address specific concerns
|
|
255
|
+
[ ] MONITOR - Not ready, reassess in [timeframe]
|
|
256
|
+
[ ] DECLINE - Does not meet partnership criteria
|
|
257
|
+
|
|
258
|
+
CONDITIONS/NEXT STEPS
|
|
259
|
+
---------------------
|
|
260
|
+
1. [Action item 1]
|
|
261
|
+
2. [Action item 2]
|
|
262
|
+
```
|
|
263
|
+
|
|
264
|
+
### Decision Matrix
|
|
265
|
+
|
|
266
|
+
| Score Range | Recommendation |
|
|
267
|
+
|-------------|----------------|
|
|
268
|
+
| 8.0-10.0 | Strong candidate, proceed |
|
|
269
|
+
| 6.5-7.9 | Good candidate, minor conditions |
|
|
270
|
+
| 5.0-6.4 | Moderate candidate, significant conditions |
|
|
271
|
+
| 3.5-4.9 | Weak candidate, consider monitoring |
|
|
272
|
+
| <3.5 | Not recommended at this time |
|
|
273
|
+
|
|
274
|
+
## Communication Guidelines
|
|
275
|
+
|
|
276
|
+
### Internal Reporting Standards
|
|
277
|
+
- Use objective, data-driven language
|
|
278
|
+
- Cite specific metrics and timeframes
|
|
279
|
+
- Document all sources of information
|
|
280
|
+
- Flag any data limitations or gaps
|
|
281
|
+
- Provide clear, actionable recommendations
|
|
@@ -0,0 +1,121 @@
|
|
|
1
|
+
# Curator Scoring Rubric
|
|
2
|
+
|
|
3
|
+
## Detailed Scoring Criteria
|
|
4
|
+
|
|
5
|
+
### 1. Track Record (25%)
|
|
6
|
+
|
|
7
|
+
| Score | Criteria |
|
|
8
|
+
|-------|----------|
|
|
9
|
+
| 10 | >3 years active, impeccable record, industry recognition |
|
|
10
|
+
| 9 | 2-3 years active, consistent excellence, no incidents |
|
|
11
|
+
| 8 | 1-2 years active, strong performance, minor issues resolved |
|
|
12
|
+
| 7 | 1-2 years active, good performance, learning visible |
|
|
13
|
+
| 6 | 6-12 months active, promising trajectory |
|
|
14
|
+
| 5 | 6-12 months active, adequate performance |
|
|
15
|
+
| 4 | 3-6 months active, limited data, some promise |
|
|
16
|
+
| 3 | 3-6 months active, concerning patterns |
|
|
17
|
+
| 2 | <3 months active, insufficient history |
|
|
18
|
+
| 1 | New or problematic history |
|
|
19
|
+
|
|
20
|
+
### 2. AUM & Growth (20%)
|
|
21
|
+
|
|
22
|
+
| Score | AUM | Growth (90d) |
|
|
23
|
+
|-------|-----|--------------|
|
|
24
|
+
| 10 | >$50M | >20% |
|
|
25
|
+
| 9 | $20-50M | >15% |
|
|
26
|
+
| 8 | $10-20M | >10% |
|
|
27
|
+
| 7 | $5-10M | >5% |
|
|
28
|
+
| 6 | $2-5M | >0% |
|
|
29
|
+
| 5 | $1-2M | Stable |
|
|
30
|
+
| 4 | $500K-1M | Stable |
|
|
31
|
+
| 3 | $250-500K | Any |
|
|
32
|
+
| 2 | $100-250K | Any |
|
|
33
|
+
| 1 | <$100K | Any |
|
|
34
|
+
|
|
35
|
+
### 3. Performance (20%)
|
|
36
|
+
|
|
37
|
+
| Score | APR vs Protocol Avg | Consistency |
|
|
38
|
+
|-------|---------------------|-------------|
|
|
39
|
+
| 10 | >50% above | Excellent (CV <10%) |
|
|
40
|
+
| 9 | 30-50% above | Very good (CV <15%) |
|
|
41
|
+
| 8 | 15-30% above | Good (CV <20%) |
|
|
42
|
+
| 7 | 5-15% above | Good (CV <25%) |
|
|
43
|
+
| 6 | At average | Acceptable (CV <30%) |
|
|
44
|
+
| 5 | 0-10% below | Acceptable |
|
|
45
|
+
| 4 | 10-20% below | Variable |
|
|
46
|
+
| 3 | 20-30% below | Inconsistent |
|
|
47
|
+
| 2 | 30-50% below | Poor |
|
|
48
|
+
| 1 | >50% below | Very poor |
|
|
49
|
+
|
|
50
|
+
### 4. Risk Management (20%)
|
|
51
|
+
|
|
52
|
+
| Score | Avg Risk Score | Volatility Management |
|
|
53
|
+
|-------|----------------|----------------------|
|
|
54
|
+
| 10 | <20 | Excellent controls documented |
|
|
55
|
+
| 9 | 20-30 | Strong risk framework |
|
|
56
|
+
| 8 | 30-40 | Good risk awareness |
|
|
57
|
+
| 7 | 40-50 | Adequate for strategy |
|
|
58
|
+
| 6 | 40-50 | Basic risk management |
|
|
59
|
+
| 5 | 50-60 | Acceptable with monitoring |
|
|
60
|
+
| 4 | 50-60 | Needs improvement |
|
|
61
|
+
| 3 | 60-70 | Concerning |
|
|
62
|
+
| 2 | 70-80 | High risk, poor controls |
|
|
63
|
+
| 1 | >80 | Unacceptable risk |
|
|
64
|
+
|
|
65
|
+
### 5. Strategy Clarity (15%)
|
|
66
|
+
|
|
67
|
+
| Score | Documentation | Communication |
|
|
68
|
+
|-------|---------------|---------------|
|
|
69
|
+
| 10 | Comprehensive, detailed | Proactive, responsive |
|
|
70
|
+
| 9 | Thorough documentation | Very responsive |
|
|
71
|
+
| 8 | Good documentation | Responsive |
|
|
72
|
+
| 7 | Adequate documentation | Generally responsive |
|
|
73
|
+
| 6 | Basic documentation | Responsive when contacted |
|
|
74
|
+
| 5 | Minimal documentation | Adequate communication |
|
|
75
|
+
| 4 | Sparse documentation | Slow to respond |
|
|
76
|
+
| 3 | Poor documentation | Poor communication |
|
|
77
|
+
| 2 | Very limited info | Unresponsive |
|
|
78
|
+
| 1 | Opaque/no info | No communication |
|
|
79
|
+
|
|
80
|
+
## Comparative Analysis Template
|
|
81
|
+
|
|
82
|
+
### Side-by-Side Comparison
|
|
83
|
+
|
|
84
|
+
| Criterion | Curator A | Curator B | Curator C |
|
|
85
|
+
|-----------|-----------|-----------|-----------|
|
|
86
|
+
| Track Record | [X]/10 | [X]/10 | [X]/10 |
|
|
87
|
+
| AUM & Growth | [X]/10 | [X]/10 | [X]/10 |
|
|
88
|
+
| Performance | [X]/10 | [X]/10 | [X]/10 |
|
|
89
|
+
| Risk Mgmt | [X]/10 | [X]/10 | [X]/10 |
|
|
90
|
+
| Strategy | [X]/10 | [X]/10 | [X]/10 |
|
|
91
|
+
| **TOTAL** | **[X]/10** | **[X]/10** | **[X]/10** |
|
|
92
|
+
|
|
93
|
+
### Partnership Priority
|
|
94
|
+
|
|
95
|
+
1. [Curator]: [Score] - [Key differentiator]
|
|
96
|
+
2. [Curator]: [Score] - [Key differentiator]
|
|
97
|
+
3. [Curator]: [Score] - [Key differentiator]
|
|
98
|
+
|
|
99
|
+
## Red Flag Checklist
|
|
100
|
+
|
|
101
|
+
### Hard No (Any one = Decline)
|
|
102
|
+
- [ ] Anonymous/unverifiable team
|
|
103
|
+
- [ ] History of exploits or security breaches
|
|
104
|
+
- [ ] Regulatory action or legal issues
|
|
105
|
+
- [ ] Evidence of fraudulent activity
|
|
106
|
+
- [ ] Refusal to provide basic information
|
|
107
|
+
|
|
108
|
+
### Serious Concern (2+ = Likely Decline)
|
|
109
|
+
- [ ] <3 months track record
|
|
110
|
+
- [ ] AUM <$250K
|
|
111
|
+
- [ ] Risk score >70 without justification
|
|
112
|
+
- [ ] APR >50% without clear yield source
|
|
113
|
+
- [ ] No strategy documentation
|
|
114
|
+
- [ ] Unresponsive to inquiries
|
|
115
|
+
|
|
116
|
+
### Monitor Closely (Note but not disqualifying)
|
|
117
|
+
- [ ] 3-6 months track record
|
|
118
|
+
- [ ] Single vault concentration
|
|
119
|
+
- [ ] Recent significant TVL changes
|
|
120
|
+
- [ ] Strategy pivots
|
|
121
|
+
- [ ] Limited team information
|
|
@@ -0,0 +1,95 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: lagoon-customer-support
|
|
3
|
+
version: 1.0.0
|
|
4
|
+
description: Consistent, professional support responses for the internal support team
|
|
5
|
+
audience: internal-support
|
|
6
|
+
category: support
|
|
7
|
+
triggers:
|
|
8
|
+
- support response
|
|
9
|
+
- customer question
|
|
10
|
+
- support template
|
|
11
|
+
- customer issue
|
|
12
|
+
- help response
|
|
13
|
+
- support ticket
|
|
14
|
+
- customer inquiry
|
|
15
|
+
- support reply
|
|
16
|
+
- escalation
|
|
17
|
+
- customer complaint
|
|
18
|
+
- support message
|
|
19
|
+
- ticket response
|
|
20
|
+
tools:
|
|
21
|
+
- search_vaults
|
|
22
|
+
- get_vault_data
|
|
23
|
+
- get_transactions
|
|
24
|
+
estimated_tokens: 2400
|
|
25
|
+
---
|
|
26
|
+
|
|
27
|
+
# Lagoon Customer Support: Response Guide
|
|
28
|
+
|
|
29
|
+
You are a support specialist helping the Lagoon support team craft consistent, helpful responses to customer inquiries. Your goal is to provide accurate, empathetic support that resolves issues efficiently.
|
|
30
|
+
|
|
31
|
+
## When This Skill Activates
|
|
32
|
+
|
|
33
|
+
This skill is relevant when support team members:
|
|
34
|
+
- Need to respond to customer inquiries
|
|
35
|
+
- Want templates for common issues
|
|
36
|
+
- Need guidance on escalation procedures
|
|
37
|
+
- Require consistent messaging for support tickets
|
|
38
|
+
- Are handling complaints or issues
|
|
39
|
+
|
|
40
|
+
## Support Response Framework
|
|
41
|
+
|
|
42
|
+
### Response Structure
|
|
43
|
+
|
|
44
|
+
Every support response should follow this structure:
|
|
45
|
+
|
|
46
|
+
1. **Acknowledgment**: Recognize the customer's situation
|
|
47
|
+
2. **Clarification**: If needed, ask targeted questions
|
|
48
|
+
3. **Solution/Information**: Provide clear, actionable guidance
|
|
49
|
+
4. **Next Steps**: Outline what happens next
|
|
50
|
+
5. **Availability**: Offer continued support
|
|
51
|
+
|
|
52
|
+
### Tone Guidelines
|
|
53
|
+
|
|
54
|
+
- **Professional but friendly**: Not robotic, not overly casual
|
|
55
|
+
- **Empathetic**: Acknowledge frustrations or concerns
|
|
56
|
+
- **Clear**: Avoid jargon unless customer uses it
|
|
57
|
+
- **Concise**: Respect customer's time
|
|
58
|
+
- **Proactive**: Anticipate follow-up questions
|
|
59
|
+
|
|
60
|
+
## Common Issue Categories
|
|
61
|
+
|
|
62
|
+
### 1. Deposit Issues
|
|
63
|
+
- Can't deposit, deposit pending, deposit failed
|
|
64
|
+
- Use `get_vault_data` to check vault status
|
|
65
|
+
|
|
66
|
+
### 2. Redemption Issues
|
|
67
|
+
- Can't redeem, redemption delayed, incorrect amount
|
|
68
|
+
- Use `get_vault_data` and `get_transactions`
|
|
69
|
+
|
|
70
|
+
### 3. Performance Questions
|
|
71
|
+
- Questions about APR, returns, comparisons
|
|
72
|
+
- Use `get_vault_performance`, `get_vault_data`
|
|
73
|
+
|
|
74
|
+
### 4. Risk Questions
|
|
75
|
+
- Concerns about safety, risk levels, security
|
|
76
|
+
- Use `analyze_risk`, `get_vault_data`
|
|
77
|
+
|
|
78
|
+
### 5. Technical Issues
|
|
79
|
+
- UI bugs, connection problems, display errors
|
|
80
|
+
- Diagnostic troubleshooting steps
|
|
81
|
+
|
|
82
|
+
## Escalation Procedures
|
|
83
|
+
|
|
84
|
+
### When to Escalate
|
|
85
|
+
|
|
86
|
+
**Immediate** (1 hour): Security concerns, >$100K transactions, legal inquiries
|
|
87
|
+
**Standard** (4 hours): Complex technical, repeated failures, unresolved after 2 interactions
|
|
88
|
+
**Scheduled** (next business day): General feedback, minor UI issues
|
|
89
|
+
|
|
90
|
+
## Communication Guidelines
|
|
91
|
+
|
|
92
|
+
- Use "we" when referring to Lagoon
|
|
93
|
+
- Avoid technical jargon unless customer is technical
|
|
94
|
+
- Never promise specific returns or outcomes
|
|
95
|
+
- Always include appropriate disclaimers
|
|
@@ -0,0 +1,196 @@
|
|
|
1
|
+
# Support Response Templates
|
|
2
|
+
|
|
3
|
+
## Quick Responses
|
|
4
|
+
|
|
5
|
+
### Deposit Received
|
|
6
|
+
```
|
|
7
|
+
Hi [Name],
|
|
8
|
+
|
|
9
|
+
Great news! Your deposit of [amount] has been successfully processed and is now earning yield in [vault name].
|
|
10
|
+
|
|
11
|
+
Current position: [X] shares
|
|
12
|
+
Current value: $[X]
|
|
13
|
+
|
|
14
|
+
You can view your position at any time in your dashboard.
|
|
15
|
+
|
|
16
|
+
Best regards,
|
|
17
|
+
[Support Agent]
|
|
18
|
+
```
|
|
19
|
+
|
|
20
|
+
### Redemption Processed
|
|
21
|
+
```
|
|
22
|
+
Hi [Name],
|
|
23
|
+
|
|
24
|
+
Your redemption has been processed successfully!
|
|
25
|
+
|
|
26
|
+
Amount redeemed: [X] [asset]
|
|
27
|
+
Transaction: [hash link]
|
|
28
|
+
|
|
29
|
+
The funds should appear in your wallet shortly (usually within a few minutes depending on network conditions).
|
|
30
|
+
|
|
31
|
+
Best regards,
|
|
32
|
+
[Support Agent]
|
|
33
|
+
```
|
|
34
|
+
|
|
35
|
+
### Request More Information
|
|
36
|
+
```
|
|
37
|
+
Hi [Name],
|
|
38
|
+
|
|
39
|
+
Thank you for contacting Lagoon support. I'd like to help resolve this for you.
|
|
40
|
+
|
|
41
|
+
To assist you better, could you please provide:
|
|
42
|
+
- [Specific information needed]
|
|
43
|
+
- [Additional context]
|
|
44
|
+
|
|
45
|
+
Once I have this information, I'll be able to investigate further.
|
|
46
|
+
|
|
47
|
+
Best regards,
|
|
48
|
+
[Support Agent]
|
|
49
|
+
```
|
|
50
|
+
|
|
51
|
+
### Issue Resolved
|
|
52
|
+
```
|
|
53
|
+
Hi [Name],
|
|
54
|
+
|
|
55
|
+
I'm pleased to confirm that your issue has been resolved.
|
|
56
|
+
|
|
57
|
+
Summary:
|
|
58
|
+
- Issue: [Brief description]
|
|
59
|
+
- Resolution: [What was done]
|
|
60
|
+
- Current Status: [Resolved/Monitoring]
|
|
61
|
+
|
|
62
|
+
Is there anything else I can help you with?
|
|
63
|
+
|
|
64
|
+
Best regards,
|
|
65
|
+
[Support Agent]
|
|
66
|
+
```
|
|
67
|
+
|
|
68
|
+
### Scheduled Maintenance
|
|
69
|
+
```
|
|
70
|
+
Hi [Name],
|
|
71
|
+
|
|
72
|
+
Thank you for your patience. The [feature/service] is currently undergoing scheduled maintenance.
|
|
73
|
+
|
|
74
|
+
Expected duration: [timeframe]
|
|
75
|
+
Impact: [What is affected]
|
|
76
|
+
Workaround: [If any]
|
|
77
|
+
|
|
78
|
+
We'll notify you when service is restored. Your funds remain safe during this maintenance period.
|
|
79
|
+
|
|
80
|
+
Best regards,
|
|
81
|
+
[Support Agent]
|
|
82
|
+
```
|
|
83
|
+
|
|
84
|
+
## FAQ Responses
|
|
85
|
+
|
|
86
|
+
### What are vault fees?
|
|
87
|
+
```
|
|
88
|
+
Lagoon vaults have transparent fee structures:
|
|
89
|
+
|
|
90
|
+
- Management Fee: [X]% annually (accrued daily)
|
|
91
|
+
- Performance Fee: [X]% of profits (only charged on gains)
|
|
92
|
+
- Entry/Exit Fees: [Details if applicable]
|
|
93
|
+
|
|
94
|
+
These fees are automatically deducted and reflected in your share value. The displayed APR is already net of fees.
|
|
95
|
+
|
|
96
|
+
For specific vault fees, you can find them on the vault details page or I can look them up for you.
|
|
97
|
+
```
|
|
98
|
+
|
|
99
|
+
### How is APR calculated?
|
|
100
|
+
```
|
|
101
|
+
APR (Annual Percentage Rate) represents the annualized return based on recent vault performance.
|
|
102
|
+
|
|
103
|
+
Calculation method:
|
|
104
|
+
- Based on [30-day/7-day] historical performance
|
|
105
|
+
- Annualized for comparison purposes
|
|
106
|
+
- Net of all fees
|
|
107
|
+
- Does not include compounding effects
|
|
108
|
+
|
|
109
|
+
Important: APR is variable and based on historical data. It does not guarantee future returns.
|
|
110
|
+
```
|
|
111
|
+
|
|
112
|
+
### What happens if a vault strategy fails?
|
|
113
|
+
```
|
|
114
|
+
While rare, strategy issues are possible in DeFi. Here's what you should know:
|
|
115
|
+
|
|
116
|
+
Protections in place:
|
|
117
|
+
- Professional curator oversight
|
|
118
|
+
- Diversified underlying strategies
|
|
119
|
+
- Regular monitoring and rebalancing
|
|
120
|
+
|
|
121
|
+
If issues occur:
|
|
122
|
+
- Curator may pause deposits/redemptions temporarily
|
|
123
|
+
- Strategy adjustments made as needed
|
|
124
|
+
- Communication sent to all depositors
|
|
125
|
+
|
|
126
|
+
Risk reminder: All DeFi investments carry risk, including potential total loss.
|
|
127
|
+
```
|
|
128
|
+
|
|
129
|
+
### How do I contact support?
|
|
130
|
+
```
|
|
131
|
+
You can reach Lagoon support through:
|
|
132
|
+
|
|
133
|
+
- This support chat (fastest response)
|
|
134
|
+
- Email: support@lagoon.protocol
|
|
135
|
+
- Discord: [link to support channel]
|
|
136
|
+
|
|
137
|
+
Support hours: [Hours]
|
|
138
|
+
Average response time: [Timeframe]
|
|
139
|
+
|
|
140
|
+
For urgent security concerns, please use [emergency contact method].
|
|
141
|
+
```
|
|
142
|
+
|
|
143
|
+
## Closing Messages
|
|
144
|
+
|
|
145
|
+
### Positive Resolution
|
|
146
|
+
```
|
|
147
|
+
I'm glad I could help resolve this for you! If you have any other questions in the future, don't hesitate to reach out.
|
|
148
|
+
|
|
149
|
+
Thank you for using Lagoon!
|
|
150
|
+
```
|
|
151
|
+
|
|
152
|
+
### Awaiting Customer Response
|
|
153
|
+
```
|
|
154
|
+
I'll keep this ticket open while awaiting your response. Feel free to reply whenever convenient.
|
|
155
|
+
|
|
156
|
+
This ticket will auto-close after [X] days of inactivity, but you can always open a new one if needed.
|
|
157
|
+
```
|
|
158
|
+
|
|
159
|
+
### After Escalation
|
|
160
|
+
```
|
|
161
|
+
I've escalated this to our specialized team who will follow up with you directly.
|
|
162
|
+
|
|
163
|
+
Ticket reference: [number]
|
|
164
|
+
Expected follow-up: [timeframe]
|
|
165
|
+
|
|
166
|
+
Thank you for your patience.
|
|
167
|
+
```
|
|
168
|
+
|
|
169
|
+
## Escalation Template
|
|
170
|
+
|
|
171
|
+
```
|
|
172
|
+
ESCALATION REQUEST
|
|
173
|
+
==================
|
|
174
|
+
|
|
175
|
+
Priority: [Critical/High/Medium/Low]
|
|
176
|
+
Category: [Technical/Financial/Security/Other]
|
|
177
|
+
|
|
178
|
+
Customer: [Name/ID]
|
|
179
|
+
Contact: [Email]
|
|
180
|
+
Original Ticket: [Number]
|
|
181
|
+
|
|
182
|
+
Issue Summary:
|
|
183
|
+
[Brief description]
|
|
184
|
+
|
|
185
|
+
Attempted Resolution:
|
|
186
|
+
[What has been tried]
|
|
187
|
+
|
|
188
|
+
Escalation Reason:
|
|
189
|
+
[Why this needs escalation]
|
|
190
|
+
|
|
191
|
+
Requested Action:
|
|
192
|
+
[What is needed from escalation team]
|
|
193
|
+
|
|
194
|
+
Supporting Information:
|
|
195
|
+
[Transaction hashes, screenshots, etc.]
|
|
196
|
+
```
|