AgentStack
Sign in Publish
MCP servers Skills Toolkits Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Repo To Wiki

skill-arnie016-codex-prompt-templates-repo-to-wiki · by Arnie016

>

↗ Website ↗ Repository
— No reviews yet
0 installs
2 views
0.0% view→install

Install

$ agentstack add skill-arnie016-codex-prompt-templates-repo-to-wiki

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • ✓ Prompt-injection patterns
  • ✓ Secret / credential exfiltration
  • ✓ Dangerous shell & filesystem operations
  • ✓ Untrusted network calls
  • ✓ Known-malicious package signatures

What it can access

  • ✓ Network access No
  • ✓ Filesystem access No
  • ✓ Shell / process execution No
  • ✓ Environment & secrets No
  • ✓ Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Repo To Wiki? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Repo To Wiki

Turn source files into stable markdown pages that future Codex sessions can read instead of rediscovering the project.

Folder Shape

wiki/
  overview.md
  architecture.md
  setup.md
  concepts/
  decisions/
  sources.md

Build Order

  1. Create wiki/sources.md with repo URLs, local paths, commit/date if known.
  2. Create wiki/overview.md from README and manifests.
  3. Create wiki/architecture.md from entry points and module layout.
  4. Create focused concept pages only when they remove repeated context.
  5. Cross-link pages with relative markdown links.

Page Contract

Each page should include:

  • purpose
  • evidence/source files
  • current understanding
  • open questions
  • last reviewed date

Rules

  • Source files remain the source of truth.
  • Keep wiki pages concise and updateable.
  • Do not invent details when source evidence is thin.
  • Use exact file links or paths for traceability.

Reference pattern source: sources/llmwiki.

Skip When

  • The user only needs a short one-time repo summary.
  • Source evidence is too thin to maintain living docs.

Validation

  • Wiki pages cite source files or URLs and last-reviewed dates.
  • Broad examples stay in concept/reference pages, not the overview.
  • Open questions are preserved instead of inventing missing architecture.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Write a review

Versions

  • v0.1.0 Imported from the upstream source.

More in AI & ML