Skills data-structure-protocol
📦

data-structure-protocol

Content revision r2 Safe ⚙️ External commands🌐 Network access

Map Codebase Structure with DSP

Large repositories force coding agents to rediscover structure during every task. DSP stores a queryable dependency graph with stable identities and explicit connection reasons.

Supports: Claude Codex Code(CC)
🥉 78 Bronze

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request
Review the Skillstore skill "data-structure-protocol" from https://skillstore.io/skills/sickn33-data-structure-protocol.md and its manifest at https://skillstore.io/api/skills/sickn33-data-structure-protocol/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/sickn33-data-structure-protocol.md Signed manifest GET /api/skills/sickn33-data-structure-protocol/manifest Signed lockfile GET /api/skills/sickn33-data-structure-protocol/lockfile

Test it

Using "data-structure-protocol". Map the authentication service and explain its dependencies.

Expected outcome:

  • Authentication is owned by the user service module.
  • It imports token validation for session checks and user storage for account lookup.
  • Its public login operation is used by the API and administration modules.

Using "data-structure-protocol". Assess the impact of replacing the utility library.

Expected outcome:

  • The utility library has five direct recipients across three modules.
  • Date formatting and collection helpers require separate migration paths.
  • Update shared services first, then validate API and reporting recipients.

Using "data-structure-protocol". Update DSP after moving the payment module.

Expected outcome:

The payment entity keeps its stable identifier, receives the new source path, and retains all import and recipient relationships.

Security Audit

Safe
v5 • 7/23/2026 Open versioned report

Two linked findings confirm one supply-chain risk: an unpinned Python CLI is downloaded from a mutable branch and later executed. The other 53 findings are safe Markdown, fixed local examples, metadata, or documentation links. No prompt injection or malicious intent was found.

1
Files scanned
204
Lines analyzed
2
Review items
0
False positives ignored
Capability review items (2)

These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.

High
SKILL.md:88-90
Ruby/shell backtick execution
```bash
Lines 88-90 direct a shell to download an unpinned Python script from a mutable branch. The skill later invokes that file, creating a remote supply-chain execution risk.
High
SKILL.md:89
Hardcoded URL
curl -O https://raw.githubusercontent.com/k-kolomeitsev/data-structure-protocol/main/skills/data-str
The URL downloads executable Python from the repository's mutable main branch without a checksum or signature. Later instructions run the downloaded file with project access.

Risk Factors

⚙️ External commands (50)
SKILL.md:11 SKILL.md:17 SKILL.md:21 SKILL.md:36 SKILL.md:40-43 SKILL.md:43-45 SKILL.md:45-48 SKILL.md:48-52 SKILL.md:52-56 SKILL.md:56-58 SKILL.md:58-74 SKILL.md:74-80 SKILL.md:80 SKILL.md:86-88 SKILL.md:88-90 SKILL.md:90-92 SKILL.md:92-96 SKILL.md:96-98 SKILL.md:98 SKILL.md:99 SKILL.md:102 SKILL.md:106 SKILL.md:107 SKILL.md:108 SKILL.md:109 SKILL.md:110-117 SKILL.md:117 SKILL.md:118 SKILL.md:119 SKILL.md:120 SKILL.md:121 SKILL.md:122 SKILL.md:128 SKILL.md:129 SKILL.md:130-131 SKILL.md:131 SKILL.md:132-133 SKILL.md:133-134 SKILL.md:134-135 SKILL.md:135-142 SKILL.md:142-154 SKILL.md:154-158 SKILL.md:158-164 SKILL.md:164-168 SKILL.md:168-174 SKILL.md:174-179 SKILL.md:179-180 SKILL.md:180-182 SKILL.md:182-183 SKILL.md:183-184
🌐 Network access (5)
SKILL.md:5 SKILL.md:89 SKILL.md:196 SKILL.md:197 SKILL.md:198
Audited by: codex View Audit History →
Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report
Security Assessment

Copy report link

https://skillstore.io/skills/sickn33-data-structure-protocol/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/sickn33-data-structure-protocol/security.svg)](https://skillstore.io/skills/sickn33-data-structure-protocol?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/sickn33-data-structure-protocol?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-data-structure-protocol/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/sickn33-data-structure-protocol.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>
Academic citations (APA · BibTeX · CFF)

APA citation

sickn33. (2026). data-structure-protocol security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-data-structure-protocol/audits/5

BibTeX citation

@techreport{sickn33-sickn33-data-structure-protocol-2026, author = {sickn33}, title = {data-structure-protocol security audit report (audit version 5)}, institution = {Skillstore}, year = {2026}, number = {5}, url = {https://skillstore.io/skills/sickn33-data-structure-protocol/audits/5}, 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: "data-structure-protocol security audit report (audit version 5)" version: "unspecified" type: report authors: - name: "sickn33" date-released: "2026-07-23" url: "https://skillstore.io/skills/sickn33-data-structure-protocol/audits/5" identifiers: - type: other value: "skillstore:sickn33-data-structure-protocol:audit:5" description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: High
55
Architecture
85
Maintainability
87
Content
68
Community
83
Spec Compliance

What You Can Build

Orient New Contributors

Query the graph to locate modules, public APIs, and dependency reasons before changing unfamiliar code.

Plan Safe Refactors

Trace recipients and dependency paths to estimate the impact of moving modules or replacing libraries.

Preserve Agent Context

Maintain a persistent structural map that coding agents can reuse across separate tasks and context windows.

Try These Prompts

Bootstrap a Project Map 
Initialize DSP for {project_root}. Identify entrypoints, map reachable local imports, record public exports, and explain each dependency reason.
Find a Feature 
Use the existing DSP graph to locate {feature}. Summarize relevant entities, dependencies, public APIs, and likely change points.
Synchronize Structural Changes 
After implementing {change}, update DSP for every affected file, import, export, move, or deletion. Preserve all stable identifiers.
Analyze Dependency Replacement 
Before replacing {dependency}, trace every recipient and graph path. Group impacts by module and propose a staged migration with validation steps.

Best Practices

  • Update DSP immediately after files, imports, exports, or public purposes change.
  • Write short dependency reasons that explain why each connection exists.
  • Review DSP changes with the related code changes.

Avoid

  • Do not assign entities to local variables or private helper details.
  • Do not replace stable identifiers when files move or receive new names.
  • Do not treat the graph as a substitute for tests or runtime validation.

Frequently Asked Questions

What does DSP store?
DSP stores entities, source paths, imports, public exports, dependency reasons, and reverse recipient relationships in plain text.
Does DSP analyze third-party package internals?
No. It records external packages as entities but does not traverse their internal files.
When should the graph be updated?
Update it when files, imports, exports, locations, or entity purposes change.
Does an internal implementation change require an update?
No update is needed when purpose, dependencies, public APIs, and file locations remain unchanged.
Can DSP replace source review and testing?
No. It supports navigation and impact analysis, while source review and tests validate actual behavior.
What software is required?
The documented workflow requires Python 3.10 or later and the separate DSP CLI script.

Developer Details

Author

sickn33

License

MIT

Skillstore revision

r2

Version notice

The author did not declare a version.

Repository

https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/data-structure-protocol

Ref

f9e2c34b4f19c7f3e6b0a1e93227b5f77cc12526

Maintenance freshness

7/26/2026

Usage

10 downloads · 91 views

File structure

📄 SKILL.md

More from sickn33

View all

Related Skills

View all