Kognitos bootstrap
Set up a Kognitos application workspace, verify prerequisites, and establish the initial development baseline.From its SKILL.md
npx -y skills add kognitos/kognitos-plugin --skill kognitos-bootstrapAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its file declares
Copied from the file, not written here
The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
1.7 KB, as published. Nobody here has run it
Kognitos Bootstrap
Use this skill when a repository needs to be prepared for Kognitos application development, or when you need to verify a local environment before making changes.
Default Flow
- Check for a
.env.localfile in the project root. If missing, copy assets/bootstrap-template.env to.env.localand have the user fill inKOGNITOS_TOKEN. - Source
.env.localand verify the token works by calling the list-organizations endpoint (see references/setup-checklist.md). - If
KOGNITOS_ORGANIZATION_IDorKOGNITOS_WORKSPACE_IDare empty, list the user's orgs and workspaces and help them pick values. - Run the preflight helper in scripts/preflight_check.py to verify local CLI tools.
- Use references/environment-model.md when environment boundaries need to be clarified.
When To Load More
- For the full setup checklist: references/setup-checklist.md
- For environment boundaries and URL patterns: references/environment-model.md
- For a starter
.env.localtemplate: assets/bootstrap-template.env
Notes
KOGNITOS_BASE_URLishttps://app.us-1.kognitos.comfor US customers. EU customers swapus-1foreu-1.- PATs use the
kgn_pat_prefix and authenticate viaAuthorization: Bearer <token>. - The token identifies the user, not a specific org or workspace. Org and workspace must be specified separately.