|
1
|
--- |
|
2
|
name: replit-docs |
|
3
|
description: Search Replit documentation for platform features, pricing, deployments, and capabilities. |
|
4
|
--- |
|
5
|
|
|
6
|
# Replit Docs Skill |
|
7
|
|
|
8
|
Search Replit documentation to find information about features, pricing, deployments, and platform capabilities. |
|
9
|
|
|
10
|
## When to Use |
|
11
|
|
|
12
|
Use this skill when: |
|
13
|
|
|
14
|
- You need information about Replit platform features |
|
15
|
- Looking up pricing details for plans and services |
|
16
|
- Getting deployment guidance for applications |
|
17
|
- Understanding platform capabilities and limitations |
|
18
|
- Finding solutions to common platform issues |
|
19
|
- Learning best practices for development on Replit |
|
20
|
|
|
21
|
## When NOT to Use |
|
22
|
|
|
23
|
- Integration setup (use integrations skill first, then docs for additional context) |
|
24
|
- Code debugging (use code analysis tools) |
|
25
|
- Real-time status or outages (documentation may be outdated) |
|
26
|
- Account-specific issues |
|
27
|
- General programming questions not related to Replit |
|
28
|
|
|
29
|
## Available Functions |
|
30
|
|
|
31
|
### searchReplitDocs(query) |
|
32
|
|
|
33
|
Search Replit documentation for platform information. |
|
34
|
|
|
35
|
**Parameters:** |
|
36
|
|
|
37
|
- `query` (str, required): Natural language question about Replit features, pricing, or capabilities |
|
38
|
|
|
39
|
**Returns:** Dict with `response` and `relevantPages` (list of title/url dicts) |
|
40
|
|
|
41
|
**Example:** |
|
42
|
|
|
43
|
```javascript |
|
44
|
// Get pricing information |
|
45
|
const result = await searchReplitDocs({ query: "How much does Core cost?" }); |
|
46
|
console.log(result.response); |
|
47
|
for (const page of result.relevantPages) { |
|
48
|
console.log(`${page.title}: ${page.url}`); |
|
49
|
} |
|
50
|
|
|
51
|
// Learn about deployments |
|
52
|
const result = await searchReplitDocs({ query: "How do I deploy a web app?" }); |
|
53
|
console.log(result.response); |
|
54
|
``` |
|
55
|
|
|
56
|
## Best Practices |
|
57
|
|
|
58
|
1. **Use natural language**: Write queries as complete questions with context |
|
59
|
2. **Be specific**: Include specific feature names or topics in queries |
|
60
|
3. **Check integrations first**: For setup instructions, search integrations first, then use docs for additional context |
|
61
|
4. **Verify with sources**: Check the relevant pages returned for authoritative information |
|
62
|
|
|
63
|
## Example Workflow |
|
64
|
|
|
65
|
```javascript |
|
66
|
// User asks about object storage pricing |
|
67
|
const result = await searchReplitDocs({ query: "How much does Replit object storage cost?" }); |
|
68
|
console.log(result.response); |
|
69
|
|
|
70
|
// Provide relevant documentation links |
|
71
|
for (const page of result.relevantPages) { |
|
72
|
console.log(`- ${page.title}: ${page.url}`); |
|
73
|
} |
|
74
|
``` |
|
75
|
|
|
76
|
## Limitations |
|
77
|
|
|
78
|
- Documentation may not reflect real-time service status |
|
79
|
- Cannot answer account-specific questions |
|
80
|
- For integration setup, prefer the integrations skill |
|
81
|
- General programming questions should use web search instead |