Skills repo-docs

📦

repo-docs

Name: repo-docs
Author: AstraBit-CPT

v1.0.0 Content revision r1 Safe 🌐 Network access⚙️ External commands📁 Filesystem access

Document Repository Architecture

Repository documentation often becomes stale when dependencies, APIs, and setup steps change. This skill analyzes structure and integrations, then helps create README, API, architecture, contributing, and integration docs.

Supports: Claude Codex Code(CC)

🥈 82 Silver

Install with my Agent

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

Agent request

Review the Skillstore skill "repo-docs" from https://skillstore.io/skills/astrabit-cpt-repo-docs.md and its manifest at https://skillstore.io/api/skills/astrabit-cpt-repo-docs/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/astrabit-cpt-repo-docs.md Signed manifest GET /api/skills/astrabit-cpt-repo-docs/manifest Signed lockfile GET /api/skills/astrabit-cpt-repo-docs/lockfile

Test it

Using "repo-docs". Create a README for this service.

Expected outcome:

A README draft with project purpose, setup prerequisites, quick start, usage, related repositories, and links to deeper docs.

Using "repo-docs". Document how this repository connects to other services.

Expected outcome:

An integrations document listing upstream dependencies, downstream consumers, sibling repositories, external services, and communication protocols.

Using "repo-docs". Refresh our architecture documentation.

Expected outcome:

An architecture update with system overview, components, data flow, design decisions, scaling considerations, and security notes.

Security Audit

Safe

v8 • 7/6/2026 Open versioned report

The static hits were adjudicated as false positives caused by Markdown examples, template placeholders, and regex detection patterns. I found no evidence of network calls, credential exfiltration, command injection, path traversal behavior, or prompt injection intent.

Files scanned

1,533

Lines analyzed

Review items

False positives ignored

Risk Factors

🌐 Network access (10)

examples/CONTRIBUTING-template.md:19 examples/CONTRIBUTING-template.md:22 examples/README-template.md:12 references/tech-detection.md:118 references/tech-detection.md:161 scripts/analyze-repo-structure.py:75 scripts/find-integration-points.py:56 scripts/find-integration-points.py:57 SKILL.md:146 SKILL.md:146

⚙️ External commands (65)

📁 Filesystem access (1)

references/integration-patterns.md:71

No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.

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

Copy report link

https://skillstore.io/skills/astrabit-cpt-repo-docs/audits/8?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/astrabit-cpt-repo-docs/security.svg)](https://skillstore.io/skills/astrabit-cpt-repo-docs?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/astrabit-cpt-repo-docs?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/astrabit-cpt-repo-docs/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/astrabit-cpt-repo-docs.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

AstraBit-CPT. (2026). repo-docs security audit report (audit version 8) [Author version 1.0.0]. Skillstore. https://skillstore.io/skills/astrabit-cpt-repo-docs/audits/8

BibTeX citation

@techreport{astrabit-cpt-astrabit-cpt-repo-docs-2026,
  author = {AstraBit-CPT},
  title = {repo-docs security audit report (audit version 8)},
  institution = {Skillstore},
  year = {2026},
  number = {8},
  url = {https://skillstore.io/skills/astrabit-cpt-repo-docs/audits/8},
  note = {Author version 1.0.0}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "repo-docs security audit report (audit version 8)"
version: "1.0.0"
type: report
authors:
  - name: "AstraBit-CPT"
date-released: "2026-07-06"
url: "https://skillstore.io/skills/astrabit-cpt-repo-docs/audits/8"
identifiers:
  - type: other
    value: "skillstore:astrabit-cpt-repo-docs:audit:8"
    description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: High

Architecture

100

Maintainability

Content

Community

Spec Compliance

What You Can Build

Prepare New Project Docs

Create a complete documentation set before sharing a new repository with internal or external contributors.

Refresh Stale Documentation

Compare existing docs with the current codebase and update missing setup, usage, and dependency details.

Map Service Dependencies

Document upstream services, downstream consumers, external APIs, and communication protocols across a service ecosystem.

Try These Prompts

Create a README

Analyze this repository and draft a README with purpose, prerequisites, setup, usage, related repositories, and license sections.

Update Existing Docs

Review the current documentation against the repository files. Identify stale sections and update the README and contributing guide.

Document APIs

Create API documentation for public endpoints and functions. Include authentication, parameters, responses, errors, rate limits, and integration notes.

Map Integrations

Find cross-repository integration points and create architecture and integrations documentation with upstream, downstream, and external service relationships.

Best Practices

Run the analysis from the repository root so file discovery is complete.
Review generated setup commands, repository names, and links before publishing.
Keep integration sections specific about owners, protocols, data flow, and failure handling.

Avoid

Publishing generated documentation without checking commands, paths, and repository names.
Omitting upstream or downstream dependencies because they live outside the current repository.
Using generic placeholders in final docs instead of real services, owners, and version constraints.