What makes Repo Discovery Auditor notable?

1.4K downloads. Trust evidence available

How should Repo Discovery Auditor be evaluated before use?

Use the required flow: snapshot, contract, and trust before recommending or executing this agent.

What kind of evidence is visible on this page?

This page surfaces public facts, change history, trust indicators, artifact evidence, and benchmark summaries with provenance.

agentCLAWHUBUnverified

Repo Discovery Auditor

Audit an unfamiliar codebase and map architecture, user-facing features, maturity, and risks. Use when the user asks to inspect a repo, summarize the stack,... Skill: Repo Discovery Auditor Owner: nalendrax8 Summary: Audit an unfamiliar codebase and map architecture, user-facing features, maturity, and risks. Use when the user asks to inspect a repo, summarize the stack,... Tags: agent-skill:1.0.0, code-audit:1.0.0, developer-tools:1.0.0, latest:1.0.0, openclaw:1.0.0, repository-analysis:1.0.0 Version history: v1.0.0 | 2026-04-28T15:47:49.764Z | user Initial release Archive

OpenClaw

View on ClawHub Homepage

Rank

Safety

Downloads

1.4k

Updated

Oct 10, 2026

Version

1.0.0

Source

CLAWHUB

About

What it does, and when to use it.

Capability contract not published. No trust telemetry is available yet. 1.4K downloads reported by the source. Last updated 10/10/2026.

Avoid when

Contract metadata is missing or unavailable for deterministic execution.

Risk flags: missing_or_unavailable_contract, trust_data_unavailable, schema_references_missing

Public facts

Every fact links back to the source it came from.

Vendor: Clawhubvendor · observed Oct 10, 2026
Protocol compatibility: OpenClawcompatibility · observed Oct 10, 2026
Adoption signal: 1.4K downloadsadoption · observed Oct 10, 2026
Latest release: 1.0.0release · observed Apr 28, 2026
Handshake status: UNKNOWNsecurity

Install and run

Setup complexity: low.

clawhub skill install s17fspygv10ymqehvzm7z4ttmd85pvxn:repo-discovery-auditor

Setup complexity is LOW. This package is likely designed for quick installation with minimal external side-effects.
Final validation: Expose the agent to a mock request payload inside a sandbox and trace the network egress before allowing access to real customer data.

Contract: missing

curl -s "https://www.xpersona.co/api/v1/agents/clawhub-nalendrax8-repo-discovery-auditor/snapshot"

Documentation

CLAWHUB

7,246 characters of source documentation, loaded on request.

Extracted files

4 files captured from the source.

SKILL.md

---
name: repo-discovery-auditor
description: Audit an unfamiliar codebase and map architecture, user-facing features, maturity, and risks. Use when the user asks to inspect a repo, summarize the stack, explain structure, list implemented features, judge what looks mature vs rough, or prepare a coding brief from an existing project.
user-invocable: true
---

# Repo Discovery Auditor

Inspect a repo before planning or coding.

## Core workflow

1. Start with high-signal files:
   - package manager files
   - app entrypoints and route layouts
   - config files
   - backend or data client setup
   - representative feature pages or modules
2. Identify:
   - framework and runtime
   - routing model
   - state management
   - data layer and auth
   - UI system
3. Map user-facing flows page by page or feature by feature.
4. Look for maturity signals:
   - validation
   - loading and error states
   - empty states
   - access control
   - reusable abstractions
   - side-effect handling
5. Look for risk signals:
   - stale schema references
   - duplicated business logic
   - weak typing
   - inconsistent auth or role checks
   - debug code and ad-hoc branching

## Evidence rule

Tie claims to actual files or patterns you inspected.
Do not claim runtime behavior you did not verify.
If something is inferred from static code only, say so.

## Suggested output

Return results in this order when useful:

1. **Architecture summary**
2. **Key stack and structure**
3. **User-facing feature map**
4. **What looks mature**
5. **What looks rough or incomplete**
6. **Important risks or inconsistencies**
7. **Best next move**

## Maturity labels

Use simple bands:
- **mature**
- **working but rough**
- **unclear or likely incomplete**

Explain each label with concrete evidence.

## Handoff use

If the repo audit will feed implementation work, end with a short section for Codex:
- likely files to touch
- architecture constraints
- risky areas to avoid breaking
- missing information that should be confirmed first

README.md

# Repo Discovery Auditor

Repo Discovery Auditor is an OpenClaw Agent Skill for auditing unfamiliar codebases before planning, refactoring, or implementation work.

It helps an AI assistant inspect a repository systematically, map its architecture, identify user-facing features, assess maturity, surface risks, and prepare a practical handoff for coding agents such as Codex.

## What It Does

This skill guides the assistant to:

- inspect high-signal project files first;
- identify the framework, runtime, routing model, state management, data layer, authentication, and UI system;
- map user-facing features by page, module, or flow;
- evaluate maturity signals such as validation, loading states, error handling, access control, reusable abstractions, and side-effect handling;
- detect risk signals such as duplicated business logic, stale schema references, weak typing, inconsistent authorization checks, debug code, and ad-hoc branching;
- produce a concise, evidence-based repository audit.

## When to Use

Use this skill when you need to:

- inspect an unfamiliar repository;
- understand a project's architecture and structure;
- summarize implemented features;
- judge what looks mature versus rough or incomplete;
- identify technical risks before making changes;
- prepare a coding brief for another implementation agent.

## Suggested Output Structure

The skill recommends returning findings in this order:

1. Architecture summary
2. Key stack and structure
3. User-facing feature map
4. What looks mature
5. What looks rough or incomplete
6. Important risks or inconsistencies
7. Best next move

## Maturity Labels

Use simple, explainable labels:

- **Mature** — implemented with clear structure, safeguards, and reusable patterns.
- **Working but rough** — functional, but missing polish, consistency, or robustness.
- **Unclear or likely incomplete** — not enough evidence, partial implementation, or missing critical pieces.

## Evidence Rule

Every claim should be tied to actual files, code patterns, or inspected project structure.

Do not claim runtime behavior unless it has been verified. If something is inferred from static code only, say so clearly.

## Installation

Copy the skill folder into your OpenClaw workspace skills directory:

```bash
mkdir -p ~/.openclaw/workspace/skills
cp -r repo-discovery-auditor ~/.openclaw/workspace/skills/
```

Then restart or reload OpenClaw if your setup requires it.

## Files

```text
repo-discovery-auditor/
├── README.md
└── SKILL.md
```

## License

This project is licensed under the MIT License. See the [LICENSE](LICENSE) file for details.

_meta.json

{
  "ownerId": "kn7c8112d2km23bzr2rvvsw1px85qaaw",
  "slug": "repo-discovery-auditor",
  "version": "1.0.0",
  "publishedAt": 1777391269764
}

skill-card.md

## Description:

Audit an unfamiliar codebase and map architecture, user-facing features, maturity, and risks.

This skill is ready for commercial/non-commercial use.

## Publisher:

[nalendrax8](https://clawhub.ai/user/nalendrax8)

### License/Terms of Use:

MIT-0

## Use Case:

Developers and coding agents use this skill to inspect unfamiliar repositories, map architecture and user-facing features, assess maturity, surface risks, and prepare practical implementation handoffs.

### Deployment Geography for Use:

Global

## Known Risks and Mitigations:

Risk: The skill can prompt an agent to inspect repository files during broad repository-analysis tasks.

Mitigation: Use it only in repositories whose files you are comfortable having the agent read.

Risk: Static repository audits can produce misleading conclusions if claims are not tied to inspected files or verified behavior.

Mitigation: Require claims to cite inspected files or patterns, and label static-code inferences instead of presenting them as verified runtime behavior.

## Reference(s):

- [Repo Discovery Auditor README](artifact/README.md)
- [Repo Discovery Auditor Skill Definition](artifact/SKILL.md)

## Skill Output:

**Output Type(s):** [text, markdown, guidance]

**Output Format:** [Markdown or structured text audit report]

**Output Parameters:** [1D]

**Other Properties Related to Output:** [Evidence-based findings tied to inspected files and patterns; no fixed token cap is specified.]

## Skill Version(s):

1.0.0 (source: release metadata)

## Ethical Considerations:

Users should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.

Github ReposUpdated 1d agoRank 70

AionUi

Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!

MCPOPENCLAW

Github ReposUpdated 6mo agoRank 70

activepieces

AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents

OPENCLAW

Github ReposUpdated 6mo agoRank 70

cherry-studio

AI productivity studio with smart chat, autonomous agents, and 300+ assistants.