Skip to content

Commit 15e8042

Browse files
Update bootstrap
1 parent 12ab426 commit 15e8042

File tree

1 file changed

+22
-14
lines changed

1 file changed

+22
-14
lines changed

prompts/bootstrap.md

Lines changed: 22 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -1,27 +1,35 @@
1-
---
2-
name: register a new skill
1+
```yaml
2+
name: bootstrap
3+
model: claude-3-5-sonnet-20241022
34
tools:
4-
- name: register-skill
5-
description: Register a new skill
5+
- name: tool-registration
6+
description: bootstrap a tool definition in the current session
67
parameters:
78
type: object
89
properties:
9-
name:
10+
content:
1011
type: string
11-
ref:
12+
description: the content of the tool definition
13+
name:
1214
type: string
15+
description: the name of the tool
1316
container:
14-
image: alpine:latest
17+
image: vonwig/bash_alpine
1518
volumes:
1619
- "docker-prompts:/prompts"
1720
command:
18-
- sh
19-
- "-c"
20-
- |
21-
echo "{{name}} {{ref}}" >> /prompts/skills.txt
22-
---
21+
- -c
22+
- "echo \"{{content|safe}}\" >> /prompts/{{name}}.md"
23+
- name: write_files
24+
```
2325
2426
# prompt
2527
26-
Start by asking the user for the name of the skill they want to register.
27-
Once you have a name, ask the user for a github ref. Complain if the github ref is not of the form `github:owner/repo?path=path/to/file.md`. If the user provides a valid ref, register the skill using the `register-skill` tool. Finally, ask the user if they want to register another skill.
28+
Take the following description of a task I'd like to complete, and extract the schema for a set of tool definitions that I'll need
29+
in order to run that task. The tool definitions should be in yaml and each tool should have a name, a description, and an openapi schema
30+
named `parameters`. Add the tools as a vector with a top-level field named `tools`. Each tool should have a top-level `container` field with
31+
and image, volumes, and command properties. The command properties must be a vector of arguments. The values of these properties can refer to the parameters definied in the parameters schame using
32+
moustache templates. The final yaml definition should be written into a code block of a markdown file named tools.md.
33+
34+
> add a tool that fetches all GitHub Issues from a public repository using curl. We do not need a token.
35+

0 commit comments

Comments
 (0)