Deed

The Sovereign Asset Title & Ownership Protocol. A high-fidelity cognitive framework for the immutable registration, verification, and transfer of real-world...

Security Scan

The skill's lofty claims about registering and transferring real-world titles are not supported by any concrete instructions, credentials, or integration points — this mismatch is unexplained and risky.

Purpose & Capability

The description promises ingestion of land registries, satellite imagery, smart-contract history, UCC filings, and automated issuance of deeds/arbitration. Yet the skill declares no required binaries, no env vars, no config paths, and no install — operations that legitimately require API keys, service endpoints, or tooling. The requested footprint is disproportionate (either the skill is incomplete or it expects the agent to use unrelated ambient credentials).

Instruction Scope

SKILL.md instructs the agent to ingest external data sources, perform legal analysis across jurisdictions, and 'orchestrate' issuance and dispute resolution. The instructions are high-level and give the agent broad, undefined license to access data and take actions that could have legal/financial effects, with no human approval checkpoints or concrete boundaries.

Install Mechanism

This is an instruction-only skill with no install spec and no code files, which reduces the immediate attack surface (nothing is written to disk). However, the lack of an install or integration spec contributes to incoherence with the claimed capabilities.

Credentials

No environment variables, credentials, or config paths are declared despite the skill's need to interact with external registries, imagery providers, blockchain nodes, or filing services. This absence is suspicious: a legitimate integration would declare the specific credentials it needs or at minimum document expected external endpoints and auth models.

Persistence & Privilege

always is false and the skill does not request persistent/system-level privileges. However, the skill's autonomous-invocation-capable instructions (self-executing arbitration, 'orchestrating' filings) imply potentially impactful actions; without explicit human approval steps, autonomous invocation could be dangerous. This is a usability/authorization gap rather than a direct misconfiguration.

What to consider before installing

This skill is conceptually ambitious but incomplete. It promises automated, legally consequential operations (title verification, filings, arbitration) yet provides no concrete integration points, no required credentials, and no controls (e.g., human sign-off, audit logging). Before installing or enabling this skill: 1) Ask the author for concrete integration details — which registries, APIs, and providers will be used, and exactly which environment variables or credentials are required. 2) Require explicit human-in-the-loop approval for any filing or legal action and demand an audit trail for all agent decisions. 3) Do not grant any government, banking, cloud, or blockchain keys to the agent until you have code and a security/privacy review. 4) If you plan to use it for real legal transfers, get legal counsel and insist on verifiable provenance for data sources. The current mismatch between claims and declared requirements is the main risk; more technical detail or a narrow, documented scope would be required to move this assessment toward benign.

DEED: The Immutable Sovereign Title

I. Ontological Foundation

In an era of fluid digital identities, the Deed serves as the gravitational center of ownership. It is no longer a static document but a dynamic, reasoning-aware container that holds the legal, historical, and physical metadata of an asset. This skill defines how Agentic Systems recognize "Property" across cross-jurisdictional boundaries.

II. Architectural Primitives

  "provenance": "Recursive verification of chain-of-custody since asset inception",
  "encumbrance": "Autonomous detection of liens, easements, and dormant legal claims",
  "conveyance":  "Atomic, multi-signature transfer logic with integrated escrow",
  "spatial_id":  "Standardized geospatial or cryptographic anchoring of the asset"
}```

## III. Operational Lifecycle
1. **Validation Phase**: The agent ingests raw land registry data, satellite imagery (for physical), or smart contract history (for digital) to establish a baseline of truth.
2. **Analysis Phase**: Deep-reasoning across historical case law to ensure the title is "Clear and Marketable."
3. **Execution Phase**: Orchestrating the "Deed of Trust" or "Grant Deed" issuance, ensuring compliance with local statutory requirements (e.g., UCC filings, land registry APIs).

## IV. The Gavel Protocol (Dispute Resolution)
The Deed skill includes a self-executing arbitration layer. If two agents claim the same UID, the system triggers a recursive audit of the time-stamped metadata to determine the "Superior Title."

---