MCPcopy Create free account
hub / github.com/continuedev/continue / buildImportSkillPrompt

Function buildImportSkillPrompt

extensions/cli/src/tools/skills.ts:84–115  ·  view source on GitHub ↗
(identifier: string)

Source from the content-addressed store, hash-verified

82};
83
84export function buildImportSkillPrompt(identifier: string): string {
85 return `
86# Overview
87
88The user wants to import skills.
89
90User-provided skill identifier:
91${identifier}
92
93# Guidelines
94- There can be multiple skills in a single repository.
95- Use the available tools to fetch content and write files. When you are done, briefly summarize which skill you imported and where you saved it.
96- Use the "AskQuestion" tool where required to clarify with the user.
97
98# Process:
99
100**Identifier can either be a URL or a skill name**
101
102- If it looks like a URL (for example, it starts with http:// or https://), open that URL and inspect its contents to find the code or files that define the skill.
103- If the URL is a GitHub repository, look for the skills folder. There can be multiple skills within subdirectories.
104- If it looks like a skill name, you should search for the most relevant open-source skill or repository that matches the skill identifier.
105- Ask questions to the user to clarify which skill they are referring to if there are multiple options in your findings.
106
107**Create the skill files**
108
109- The skills should be created under the directory: ~/.continue/skills/<skill-name>
110- The subdirectory name should match the name of the skill directory in the fetched repository.
111- The relevant files and folders along with SKILL.md should be present inside the created skill subdirectory.
112- If the skill already exists, ask question to the user to clarify whether they want to update it.
113- Important: Before writing any files, ask the user if they want to proceed with the import.
114`;
115}

Callers 1

handleImportSkillFunction · 0.85

Calls

no outgoing calls

Tested by

no test coverage detected