by kirodotdev
A persistent workspace for development work that self-improves and continues beyond one session.
# Add to your Claude Code skills
git clone https://github.com/kirodotdev/KiroCrewLast scanned: 8/5/2026
{
"issues": [
{
"file": "AGENTS.md",
"line": 87,
"type": "secret-exfiltration",
"message": "Instruction appears to send credentials/secrets to an external endpoint",
"severity": "medium"
},
{
"file": "README.md",
"line": 70,
"type": "remote-install",
"message": "Install command (remote install script piped to a shell — review the source before running): \"curl -fsSL https://download.crew.kiro.dev/cli.sh | sh\"",
"severity": "low"
},
{
"file": "skills/kirocrew-commands/SKILL.md",
"line": 219,
"type": "secret-exfiltration",
"message": "Instruction appears to send credentials/secrets to an external endpoint",
"severity": "medium"
},
{
"file": "src/kiro_crew/builtin_skills/artifacts/SKILL.md",
"line": 184,
"type": "prompt-injection",
"message": "Possible concealment directive: \"never tell the user\"",
"severity": "medium"
}
],
"status": "PASSED",
"scannedAt": "2026-08-05T06:27:21.249Z",
"npmAuditRan": true,
"pipAuditRan": true,
"promptInjectionRan": true
}See how KiroCrew compares with popular alternatives.
KiroCrew is an open-source ai agents skill for AI coding assistants such as Claude Code, Codex CLI, and ChatGPT, built by kirodotdev. A persistent workspace for development work that self-improves and continues beyond one session. It has 3,989 GitHub stars.
Yes. KiroCrew passed SkillsLLM's automated security scan — a dependency vulnerability audit plus prompt-injection heuristics — with no high-severity issues. You can read the full report in the Security Report section on this page.
Clone the repository with "git clone https://github.com/kirodotdev/KiroCrew" and add it to your Claude Code skills directory (see the Installation section above).
KiroCrew is primarily written in Python. It is open-source under kirodotdev on GitHub, so you can review or fork the full source.
Yes. SkillsLLM lists many other AI Agents skills you can browse and compare side by side. Open the AI Agents category from the badge at the top of this page, or use the Related Skills and comparison links further down to weigh KiroCrew against similar tools.
No comments yet. Be the first to share your thoughts!
⚠️ Third-Party Software Notice
This skill is third-party open-source software developed and hosted independently on GitHub. SkillsLLM is an informational directory and does not control or maintain the underlying repository.
Any security checks, ratings, or warnings displayed by SkillsLLM are automated and limited in scope. They do not constitute a security certification or guarantee that the software is safe, error-free, or free from malicious code, vulnerabilities, compromised dependencies, or prompt-injection risks.
Review the source code, permissions, dependencies, and configuration before installing or running any third-party skill. Use is at your own risk. To the maximum extent permitted by applicable law, SkillsLLM is not liable for losses arising from third-party software.
You choose how to run Kiro Crew: the desktop app with automatic updates, a
one-line install on your machine or a remote host, the Docker image for
always-on servers, or a build from source. The default agent runs on
kiro-cli, which you install and sign in to separately. First launch checks
that prerequisite and links to the official setup guide when it is missing.
The desktop app starts a bundled Gateway when no local Gateway is already running, updates itself on the channel you download, and can connect to a remote Gateway over an SSH tunnel. See the desktop app guide.
On Linux, start with the one-line install — it is the smoothest path, works
on every distro and both architectures, and puts kirocrew on your PATH,
which is what makes kirocrew service install (and the AppArmor profile the
agent sandbox needs on Ubuntu 23.10+) reachable:
curl -fsSL https://download.crew.kiro.dev/cli.sh | sh
You then work in the dashboard at http://localhost:5476. Add a desktop
package when you want what only the Electron shell gives you: an
application-menu entry and icon, a native window, a taskbar badge, a system-wide
hotkey, a Gateway that starts and stops with the app, and in-app updates. A
.deb or .rpm installs to a fixed path under /opt, which is what lets it set
the AppArmor profile up for you; the AppImage needs no root but needs FUSE and
carries a manual sandbox step. uname -m prints which architecture you need.
| Linux desktop package | x86_64 | aarch64 (Graviton, Raspberry Pi, ARM laptops) |
|---|---|---|
.deb (Debian, Ubuntu) |
Stable · Insider · Nightly | Stable · Insider · Nightly |
.rpm (Fedora, RHEL, CentOS Stream, Amazon Linux 2023) |
Stable · Insider · Nightly | Stable · Insider · Nightly |
| AppImage (no root, any distro) | Stable · Insider · Nightly | Stable · Insider · Nightly |
sudo apt install ./KiroCrew-x86_64.deb # Debian, Ubuntu
sudo dnf install ./KiroCrew-x86_64.rpm # Fedora, RHEL, CentOS Stream, AL2023
The Linux desktop app needs glibc 2.34 or newer (Ubuntu 22.04+, Debian 12+, Fedora, CentOS Stream 9, Amazon Linux 2023). On an older host — Ubuntu 20.04, Debian 11, Amazon Linux 2 — use the one-line install above.
Every architecture below is a first-class lane: each gets its own build, its own auto-update feed, and its own SLSA provenance attestation.
| Install path | x86_64 | aarch64 (ARM64) |
|---|---|---|
| CLI one-liner / wheel | yes | yes (the wheel is py3-none-any; native libraries are vendored per architecture) |
Desktop .deb / .rpm / AppImage |
yes | yes |
| Docker image | yes | yes (linux/amd64 and linux/arm64 under every tag, so docker pull picks yours) |
Take Stable unless you have a reason not to — the table below says who each channel is for.
Every install path — desktop app, CLI, Docker image — offers the same three channels. Pick by how much churn you can absorb, not by version number:
| Channel | Who it's for | Built from | Cadence |
|---|---|---|---|
| Stable | Everyone. The default on every install path. | The Insider build that baked long enough to be promoted | On promotion, no calendar commitment |
| Insider | Power users who want features days to weeks early and accept the new bugs that come with them | Release-branch release-candidate tags | Every RC |
| Nightly | Us and contributors. Untested main HEAD — expect breakage. |
main, 06:00 UTC daily |
Daily |
Stable and Insider are two update lanes of the same app. The desktop app
switches between them in Settings → About, a CLI install switches by re-running
the installer with --channel, and a container switches by pulling a different
tag. Either way, the other lane's current version then arrives as an ordinary
update.
Because they are one app, keeping a Stable and an Insider copy side by side
does not give you two independent installs. Both read the same desktop settings
store, so the channel is a single value and whichever copy wrote it last wins —
switch to Insider in one and the other follows. They share one update download
cache as well. KIROCREW_HOME does not separate them either: it moves the data
home, not the desktop settings.
Nightly is a separate app with its own name and icon, so it installs alongside
a Stable or Insider one rather than replacing it. That also makes it the one copy
that keeps its own channel and its own settings store. It is not a sandbox,
though: it reads the same ~/.kiro/crew data home unless you point it elsewhere
with KIROCREW_HOME.
Running Insider or Nightly is a real contribution. When something looks wrong, please open an issue so it gets fixed before it reaches Stable.
Install the prebuilt, SHA-256-verified wheel from the release CDN without
cloning the repository or running npm and a local build.
Stable, the default:
curl -fsSL https://download.crew.kiro.dev/cli.sh | sh
Track a faster channel, insider or nightly (see
Release channels for who each one is for):
curl -fsSL https://download.crew.kiro.dev/cli.sh | sh