Lists importable markdown files from a GitHub repository.
Walks the given repo via the GitHub API and returns paths to every `.md` file found, so a UI can let the user pick which one to import. The provided token is used only for this request and is not persisted. Pair with `POST SkillGenerateFromGitHub` to fetch one of the listed files and produce a draft skill definition.
Authorization
Bearer JWT Authorization header using the Bearer scheme. Enter 'Bearer' [space] and then your token.
In: header
Path Parameters
The tenant identifier
The GitHub repository details.
GitHub repository owner (user or organization name).
1 <= lengthGitHub repository name.
1 <= lengthGitHub personal access token with repo read permissions.
1 <= lengthResponse Body
curl -X POST "https://api.fruxon.com/v1/tenants/string/skills:importGithub" \ -H "Content-Type: application/json" \ -d '{ "owner": "string", "repo": "string", "token": "string" }'[
{
"path": "string",
"name": "string",
"size": 0
}
]{
"type": "string",
"title": "string",
"status": 0,
"detail": "string",
"instance": "string",
"property1": null,
"property2": null
}Retrieves a specific skill by ID.
Returns the full skill definition — instructions, tool list, and metadata — for the given ID. Returns 404 if the skill does not exist or belongs to another tenant. Built-in skills are returned the same shape as custom ones, but their `id` is a stable well-known string rather than a GUID.
Creates a new skill.
Persists a tenant-scoped skill and returns its assigned ID in the `Location` header. The skill becomes immediately eligible for agents in the same tenant — attach it via the agent configuration. To author the definition from a markdown file instead of writing it by hand, run `POST SkillGenerateFromMarkdown` or `POST SkillGenerateFromGitHub` first, then POST the result here.