# Manage Astrale Kernels with CLI Workflows

Astrale operations require precise paths, identity selection, and command options. This reference guides assistants through Kernel operations, graph workflows, diagnostics, and local UI setup.

## Install

```bash
npx skillstore add astrale-os/astrale-cli
```

## Metadata

- Status: approved
- Slug: astrale-os-astrale-cli
- Skillstore revision: r1
- Version status: missing
- Tree hash: c121e99c7df0049e1e87e401c854c0289e29803305385ce27bb5d563916d0eb0
- Author: astrale-os
- GitHub username: astrale-os
- License: MIT
- Repository: https://github.com/astrale-os/cli/tree/db2fc39650aa2fbd37e8439804d5e627ac83bcb0/skills/astrale-cli
- Ref: e406bf64b5db6e514879399e87b346fa7ff7c2fb
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, network, filesystem
- Quality score: 69
- Public page: https://skillstore.pages.dev/skills/astrale-os-astrale-cli
- Manifest: https://skillstore.pages.dev/api/skills/astrale-os-astrale-cli/manifest

## Capabilities

- Guides instance selection, bookmarks, invitations, and authorized root identity recovery.
- Explains canonical Kernel paths, node reads, schema introspection, and paginated graph queries.
- Documents atomic graph mutations, callable input handling, dry runs, and binary output.
- Explains domain installation, release verification, issuer consent, and uninstall modes.
- Guides local UI initialization, component search, source installation, and project checks.
- Documents identity selection, credential delegation, journal filtering, and authenticated browser sessions.

## Use Cases

- Inspect Application Graph Data: Read nodes, inspect callable schemas, and paginate bounded graph queries on an explicitly selected instance.
- Plan Domain Updates: Review installed releases, dependency compatibility, and issuer changes before approving a grouped domain installation.
- Configure Local UI Projects: Initialize React and Tailwind CSS projects, search available patterns, and review source changes before adding components.

## Prompt Templates

### Check Connection and Identity

```
Use astrale-cli to explain read-only connection and identity checks for staging. Do not print tokens or change configuration.
```

### Prepare a Paginated Graph Query

```
Prepare a bounded query for /:notes.example:class.Note on staging using identity reader. Explain cursor pagination without running mutations.
```

### Review a Mutation Before Execution

```
Review mutation.v3.json and prepare an Astrale mutation dry run. Explain preconditions and atomicity; require approval before execution.
```

### Plan an Authorized Domain Upgrade

```
Plan a grouped domain upgrade on staging. Review release pins, compatibility, and issuer consent using an authorized identity; require approval before installation.
```

## Limitations

- Provides documentation only; the Astrale CLI package and its implementation are not bundled.
- Requires Node 22 or newer and authorized access to existing Kernels for remote operations.
- Does not build, deploy, or publish domains; those workflows belong to the separate astrale-domain binary.
- Managed instance operations require a configured Admin Domain; permissions can limit inventory and query results.

## Best Practices

- Select the instance and least-privileged identity explicitly, and verify current command help before remote operations.
- Review dry runs and release pins; approve mutations, issuer changes, root recovery, and destructive uninstalls explicitly.
- Prefer identity selection over bearer arguments; keep secret payloads in protected files or stdin, and redact shared diagnostics.

## Anti Patterns

- Relying on an ambient active instance or root identity for unattended production changes.
- Placing bearer credentials or secret payloads in command arguments, logs, or issue reports.
- Treating partial domain inventory or authorization-masked reads as proof that data is missing.

## Security Audit

- Audited at: 2026-10-10T14:10:07.537\+00:00
- Summary: All 269 static findings are documentation false positives, including Markdown delimiters, example URLs, and descriptions of owner-private credential caches. Token examples introduce one semantic risk by passing bearer credentials through command-line arguments. No evidence found of prompt injection, malicious exfiltration, or unauthorized execution; external CLI implementation was not included.

## Stats

- Views: 0
- Downloads: 1
- Favorites: 0
- Popularity score: 0