📦

astrale-domain

Name: astrale-domain
Author: astrale-os

Révision du contenu r1 Sûr 📁 Accès au système de fichiers🌐 Accès réseau⚙️ Commandes externes

Build and Maintain Astrale Domains

Astrale Domain development spans Schema, authorization, runtime, and deployment, which can become inconsistent. This skill guides focused changes and phased creation with explicit verification boundaries.

Prend en charge: Claude Codex Code(CC)

📊 76 Adéquat

Maintain this Skill? Claim it 📊 76 Adéquat

Installer avec mon Agent

Copiez cette demande dans votre Agent. Elle contient la page Skill de référence et le manifeste.

Demande d’agent

Review the Skillstore skill "astrale-domain" from https://skillstore.io/skills/astrale-os-astrale-domain.md and its manifest at https://skillstore.io/api/skills/astrale-os-astrale-domain/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Votre Agent doit toujours présenter son plan et demander toute confirmation exigée par la politique de sécurité.

Ressources lisibles par les agents

Utilisez ces liens lorsqu’un Agent IA, un crawler ou un script a besoin d’un contexte propre au lieu de lire toute la page.

Détail Markdown GET /skills/astrale-os-astrale-domain.md manifest signé GET /api/skills/astrale-os-astrale-domain/manifest lockfile signé GET /api/skills/astrale-os-astrale-domain/lockfile

Tester

Utilisation de « astrale-domain ». Review a proposed Issue.close callable.

Résultat attendu:

Declare the callable input, output, authentication mode, and Policy in Schema.
Implement the admitted operation as a Workflow with named read and mutation steps.
Guard the state transition atomically rather than trusting the earlier read.
Test an allowed call, a Policy refusal, and a stale-state refusal.

Utilisation de « astrale-domain ». Plan an upgrade where employees depends on agencies.

Résultat attendu:

Rebuild employees against the candidate agencies Schema revision.
Deploy both candidates and verify their served release metadata.
Install both as explicit roots in one grouped operation after approval.
Inspect installed revisions and retained behavior; preserve operation identity if the outcome is unknown.

Utilisation de « astrale-domain ». Diagnose a callable that works as Root but fails for a user.

Résultat attendu:

Confirm the installed release, callable key, and registered caller identity.
Inspect the authenticated principal ceiling separately from caller Policy admission.
Verify the intended caller or self session and exact Domain requirements.
Repeat allowed and refused calls, then independently verify that refusal caused no effects.

Audit de sécurité

Sûr

v1 • 10/10/2026 Ouvrir le rapport versionné

All 61 static findings are false positives in their documented context, including Markdown backticks, public discovery paths, and authorized deployment examples. Secret references configure deployment environments, and identity guidance explicitly prohibits private-key disclosure and unauthorized registration. No evidence found of prompt injection, credential exfiltration, or malicious intent in the reviewed files.

Fichiers analysés

1,978

Lignes analysées

Éléments à examiner

Faux positifs ignorés

Facteurs de risque

📁 Accès au système de fichiers (2)

references/debugging.md:39 references/development.md:152

🌐 Accès réseau (1)

references/integrations.md:31

⚙️ Commandes externes (34)

Le dernier audit statique et sémantique terminé n’a détecté aucun constat de sécurité confirmé. Cela ne prouve pas que le skill est sans effets secondaires.

Audité par: codex

Partager et citer ce rapport

Partagez le rapport d’évaluation versionné, le badge neutre, la carte intégrable et les citations. Skillstore présente les preuves sans décider si ce Skill est sûr.

Ouvrir le rapport versionné

Copier le lien du rapport

https://skillstore.io/skills/astrale-os-astrale-domain/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Badge Markdown

[![Skillstore security assessment](https://skillstore.io/badges/skills/astrale-os-astrale-domain/security.svg)](https://skillstore.io/skills/astrale-os-astrale-domain?utm_source=security_passport_badge)

Badge HTML

<a href="https://skillstore.io/skills/astrale-os-astrale-domain?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/astrale-os-astrale-domain/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Carte intégrable

<iframe src="https://skillstore.io/embed/skills/astrale-os-astrale-domain.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

Citations académiques (APA · BibTeX · CFF)

Citation APA

astrale-os. (2026). astrale-domain security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/astrale-os-astrale-domain/audits/1

Citation BibTeX

@techreport{astrale-os-astrale-os-astrale-domain-2026,
  author = {astrale-os},
  title = {astrale-domain security audit report (audit version 1)},
  institution = {Skillstore},
  year = {2026},
  number = {1},
  url = {https://skillstore.io/skills/astrale-os-astrale-domain/audits/1},
  note = {Author version unspecified}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "astrale-domain security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
  - name: "astrale-os"
date-released: "2026-10-10"
url: "https://skillstore.io/skills/astrale-os-astrale-domain/audits/1"
identifiers:
  - type: other
    value: "skillstore:astrale-os-astrale-domain:audit:1"
    description: "Skillstore immutable audit report identifier"

Score Skillstore

Pourquoi ce score Niveau de confiance des preuves: Moyen

Architecture

Maintenabilité

Contenu

Communauté

Conformité aux spécifications

Ce que vous pouvez créer

Create a Business Domain

Guide an application developer through project inspection, Schema design, callable implementation, sample data, and verification.

Review Authorization Boundaries

Help a security engineer examine callable admission, caller and principal authority, group membership, and refusal evidence.

Qualify a Coordinated Release

Help a release engineer plan coherent dependency upgrades, grouped installs, rollback constraints, and installed-behavior checks.

Essayez ces prompts

Inspect an Existing Domain

Inspect this Astrale Domain project. Identify its Schema, runtime, environments, and verification commands. Explain missing prerequisites without deploying or changing secrets.

Add a Protected Callable

Add [operation] to [Class] using the installed SDK. Declare Schema-owned authorization and runtime behavior. Add allowed and refused tests without deploying.

Implement an External Integration

Implement [provider operation] through an Integration and Provider. Keep secrets environment-owned. Validate responses and test effects and failure behavior without claiming exactly-once delivery.

Plan a Dependency Migration

Plan [Schema change] across affected Domains. Inspect installed revisions, design staged data migration, and specify grouped installs and rollback checks. Require approval before mutations.

Bonnes pratiques

Inspect current source and installed public SDK exports before choosing API syntax.
Keep authorization in Schema, secrets in deployment environments, and tests focused on allowed and refused behavior.
Verify build, served release, installed revision, and live invocation separately before reporting deployment success.

Éviter

Do not weaken authentication or add handler authorization substitutes to make a failing test pass.
Do not put secrets in Schema, logs, test snapshots, source files, or command arguments.
Do not install coherent dependencies sequentially or treat deployment as installation.

Foire aux questions

What does this skill provide?

It provides task-routed guidance for Astrale Domain authoring, authorization, runtime, Views, testing, migration, deployment, and debugging.

Which AI tools are supported?

The marketplace lists Claude, Codex, and Claude Code. Project execution still depends on your installed Astrale tools and permissions.

Does it include the Astrale SDK or CLI?

No. It contains Markdown instructions and references. Install compatible public SDK, CLI, and adapter packages for implementation and live verification.

Does deployment update an instance?

No. Deployment creates a release endpoint. Installation separately changes the release pinned on the chosen instance.

How should secrets be handled?

Keep secrets in their owning deployment environment. Avoid source, logs, test evidence, and command arguments. Use private files or secret-manager input.

Can it guarantee safe migrations or exactly-once delivery?

No. Migration support depends on public SDK contracts, and the inline Workflow runner does not provide durable replay or exactly-once execution.