align
Semantic Rigidity Gate - Ensure each node has a single unambiguous causal role.
What this skill does
# Semantic Rigidity Gate This skill determines whether a node has a uniquely interpretable meaning in the graph. Alignment does not evaluate completeness or quality. It eliminates semantic ambiguity that would cause reasoning divergence. > [!IMPORTANT] A node is aligned only if its meaning has exactly one causal role. If multiple interpretations are > possible, alignment fails. --- ## Core Principle Validation ensures the graph can exist. Alignment ensures the graph means only one thing. If alignment fails → different agents may derive different conclusions. Alignment verifies determinism of interpretation, not properties of the node alone. Alignment guarantees that traversal meaning is path-independent. --- ## 0. Precondition The node MUST pass `validate`. If validation fails → STOP --- ## 1. Semantic Topology from Schema After confirming `validate` PASS, the agent MUST read `docgraph.toml` to derive the semantic topology used for alignment. `docgraph.toml` is the sole normative source. If unread, the agent MUST stop. The agent MUST map schema elements into interpretation constraints: - Node type → causal role candidates (e.g., UC=Intent, FR=Responsibility, MOD=Realization, ADR=Rationale) - Relation type (`r.type`) → allowed causal questions (Why/What/How/Boundary/Justification) - Which relations define "peerhood" for horizontal comparison Alignment MUST only judge determinism using this schema-derived topology. If the mapping cannot be established, alignment MUST fail (unknown semantics). --- ## 2. Role Determinism The node must belong to exactly one abstraction level: - Intent (why) - Responsibility (what) - Realization (how) - Constraint (boundary) - Rationale (justification) If the node can be interpreted as more than one → FAIL The role must be inferable from relations, not from description wording. If role changes when ignoring prose, alignment fails. --- ## 3. Vertical Determinism Parent and child relations must not redefine the node's role. Invalid cases: - Parent treats node as requirement, child treats it as implementation - Node alternates abstraction level depending on traversal direction Result: FAIL --- ## 4. Semantic Collision The graph must not provide multiple answers to the same causal question. Invalid cases: - synonymous responsibilities split across nodes - overlapping definitions describing identical behavior - two nodes satisfy the same parent relation - peer boundaries depend on interpretation Result: FAIL --- ## Minimal Tooling (Observation Only) Alignment MUST use `docgraph` for observation. Tools materialize evidence; they do not drive exploration. ### `docgraph describe` Inspect the target node and its immediate inbound/outbound relations. ```bash docgraph describe <ID> ``` ### `docgraph query` (bounded) Use bounded queries only to detect ambiguity patterns, never to discover new intent. Typical checks: - Competing parents (multiple "Why" justifications) ```bash docgraph query "MATCH (p)-[r]->(n) WHERE n.id='<ID>' RETURN p.id, p.type, r.type" ``` - Competing children (multiple "How" realizations that imply different roles) ```bash docgraph query "MATCH (n)-[r]->(c) WHERE n.id='<ID>' RETURN c.id, c.type, r.type" ``` - Peer collision (potential synonyms within the same type) ```bash docgraph query "MATCH (m:<TYPE>) RETURN m.id, m.title" ``` > [!CAUTION] Queries MUST be bounded (1-hop or limited results). If multi-hop traversal is required, switch to > `reasoning`. --- ## What Alignment Does NOT Check Alignment does not enforce: - completeness - coverage - implementation presence - formatting quality - directory structure --- ## Alignment Report ### Target - **Node**: [ID] ### Determinism Results | Check | Result | Notes | | :------------------- | :-------- | :---- | | Schema topology | READ | | | Role determinism | PASS/FAIL | | | Vertical determinism | PASS/FAIL | | | Semantic collision | PASS/FAIL | | --- ## Final Decision **PASS** → Node meaning is uniquely defined **FAIL** → Node meaning is ambiguous **FINAL DECISION: [PASS/FAIL]**
Related in Backend & APIs
jfrog
IncludedInteract with the JFrog Platform via the JFrog CLI and REST/GraphQL APIs. Use this skill when the user wants to manage Artifactory repositories, upload or download artifacts, manage builds, configure permissions, manage users and groups, work with access tokens, configure JFrog CLI servers, search artifacts, manage properties, set up replication, manage JFrog Projects, run security audits or scans, look up CVE details, query exposures scan results from JFrog Advanced Security, manage release bundles and lifecycle operations, aggregate or export platform data, or perform any JFrog Platform administration task. Also use when the user mentions jf, jfrog, artifactory, xray, distribution, evidence, apptrust, onemodel, graphql, workers, mission control, curation, advanced security, exposures, or any JFrog product name.
cupynumeric-migration-readiness
IncludedPre-migration readiness assessor for porting NumPy to cuPyNumeric. Use BEFORE substantial porting work begins when the user asks whether code will scale on GPU, whether they should migrate to cuPyNumeric, which NumPy patterns transfer cleanly, what must be refactored before porting, or mentions pre-port assessment, scaling analysis, or refactor planning. Inspect the user's source code, look up NumPy usage, cross-reference the cuPyNumeric API support manifest, and distinguish distributed-scaling-friendly patterns from blockers such as unsupported APIs, scalar synchronization, host round-trips, Python/object-heavy control flow, shape/data-dependent branching, and in-place mutation hazards. Produce a verdict of READY, LIGHT REFACTOR, SIGNIFICANT REFACTOR, or NOT RECOMMENDED, with concrete refactor pointers.
alibabacloud-data-agent-skill
IncludedInvoke Alibaba Cloud Apsara Data Agent for Analytics via CLI to perform natural language-driven data analysis on enterprise databases. Data Agent for Analytics is an intelligent data analysis agent developed by Alibaba Cloud Database team for enterprise users. It automatically completes requirement analysis, data understanding, analysis insights, and report generation based on natural language descriptions. This tool supports: discovering data resources (instances/databases/tables) managed in DMS, initiating query or deep analysis sessions, real-time progress tracking, and retrieving analysis conclusions and generated reports. Use this Skill when users need to query databases, analyze data trends, generate data reports, ask questions in natural language, or mention "Data Agent", "data analysis", "database query", "SQL analysis", "data insights".
token-optimizer
IncludedReduce OpenClaw token usage and API costs through smart model routing, heartbeat optimization, budget tracking, and native 2026.2.15 features (session pruning, bootstrap size limits, cache TTL alignment). Use when token costs are high, API rate limits are being hit, or hosting multiple agents at scale. The 4 executable scripts (context_optimizer, model_router, heartbeat_optimizer, token_tracker) are local-only — no network requests, no subprocess calls, no system modifications. Reference files (PROVIDERS.md, config-patches.json) document optional multi-provider strategies that require external API keys and network access if you choose to use them. See SECURITY.md for full breakdown.
resend-cli
IncludedUse this skill when the task is specifically about operating Resend from an AI agent, terminal session, or CI job via the official resend CLI: installing/authenticating the CLI, sending/listing/updating/cancelling emails, batch sends, domains and DNS, webhooks and local listeners, inbound receiving, contacts, topics, segments, broadcasts, templates, API keys, profiles, or debugging Resend CLI/API failures. Trigger on mentions of Resend CLI, `resend`, `resend doctor`, `resend emails send`, `resend domains`, `resend webhooks listen`, `resend emails receiving`, or agent-friendly terminal automation.
alibabacloud-odps-maxframe-coding
IncludedUse this skill for MaxFrame SDK development and documentation navigation on Alibaba Cloud MaxCompute (ODPS). Helps answer MaxFrame API, concept, official example, and supported pandas API questions; create data processing programs; read/write MaxCompute tables; debug jobs (remote or local); and build custom DPE runtime images. Trigger when users mention MaxFrame, MaxCompute with MaxFrame, ODPS table processing, DPE runtime, MaxFrame docs/examples, DataFrame/Tensor operations, or GPU runtime setup. Works for both English and Chinese queries about Alibaba Cloud data processing with MaxFrame.