Skills repo-intake-and-plan
๐Ÿ“ฆ

repo-intake-and-plan

Content revision r2 Safe โš™๏ธ External commands

Plan a Trustworthy Repository Reproduction

Repository reproduction often starts without a clear map of documented setup and experiment paths. This skill scans repository signals and recommends a minimal reproduction target.

Supports: Claude Codex Code(CC)
๐Ÿฅˆ 81 Silver

This skill is part of a pack

Install the whole pack to get every skill the task needs, in one command.

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-intake-and-plan" from https://skillstore.io/skills/lllllllama-repo-intake-and-plan.md and its manifest at https://skillstore.io/api/skills/lllllllama-repo-intake-and-plan/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.

Test it

Using "repo-intake-and-plan". Scan a vision repository and prioritize inference.

Expected outcome:

  • Repository summary: README, requirements, configs, and demo directories are present.
  • Recommended target: documented single-image inference using the provided checkpoint.
  • Open issue: the checkpoint location requires a user-supplied value.

Using "repo-intake-and-plan". Compare evaluation and training options in a language model repository.

Expected outcome:

  • Evaluation has an explicit README entrypoint and named configuration.
  • Training is documented but requires distributed resources and dataset preparation.
  • Recommendation: reproduce evaluation first and defer training.

Using "repo-intake-and-plan". Inspect a repository with incomplete documentation.

Expected outcome:

  • The repository contains packaging files and scripts but no root README.
  • Candidate categories rely on filenames and remain inferred.
  • Recommendation: request documentation before selecting an execution target.

Security Audit

Safe
v5 โ€ข 8/8/2026 Open versioned report

All four static findings are false positives caused by Markdown backticks, a regular expression, and a supported language label. The scripts read local repository metadata and README content without invoking extracted commands.

5
Files scanned
510
Lines analyzed
0
Review items
0
False positives ignored
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
Security Assessment

Copy report link

https://skillstore.io/skills/lllllllama-repo-intake-and-plan/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/lllllllama-repo-intake-and-plan/security.svg)](https://skillstore.io/skills/lllllllama-repo-intake-and-plan?utm_source=security_passport_badge)

HTML badge

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

Embed card

<iframe src="https://skillstore.io/embed/skills/lllllllama-repo-intake-and-plan.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

lllllllama. (2026). repo-intake-and-plan security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/lllllllama-repo-intake-and-plan/audits/5

BibTeX citation

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

Skillstore Score

Why this score Evidence Confidence: High
64
Architecture
85
Maintainability
87
Content
69
Community
91
Spec Compliance

What You Can Build

Triage a Research Repository

Map documented commands and select a small reproduction target before allocating compute.

Prepare an Engineering Handoff

Summarize setup files, entrypoints, and unresolved requirements for an implementation team.

Assess a Student Project

Separate inference, evaluation, and training paths before beginning a course reproduction assignment.

Try These Prompts

Basic Repository Intake
Scan {repository_path} and summarize its README, important files, documented commands, and smallest trustworthy reproduction target.
Inference-First Plan
Inspect {repository_path}, prioritize documented inference commands, identify required substitutions, and recommend the smallest runnable inference path.
Compare Experiment Paths
Classify documented commands in {repository_path} as inference, evaluation, training, or other, then compare their evidence and expected complexity.
Conservative Reproduction Handoff
Audit {repository_path} for explicit README evidence, distinguish documented facts from inferences, list ambiguities, and produce a minimal plan for the orchestrator.

Best Practices

  • Provide the repository root and state whether inference, evaluation, or training has priority.
  • Treat extracted commands as evidence for planning, not as approved execution instructions.
  • Resolve every reported placeholder and ambiguity before environment setup or execution.

Avoid

  • Do not ask this skill to install dependencies or run experiments.
  • Do not treat filename-based classifications as confirmed documentation.
  • Do not select expensive training when a documented inference or evaluation target meets the goal.

Frequently Asked Questions

Does this skill execute repository commands?
No. It extracts and classifies commands for planning only.
Which repository files does it inspect first?
It prioritizes README, environment, packaging, setup, and Docker files at the repository root.
How are commands classified?
README section headings, script names, and command terms indicate inference, evaluation, training, or other categories.
Can it identify required command values?
Yes. It flags angle-bracket placeholders that require researcher-supplied values.
Does it verify that documentation is correct?
No. It reports documented evidence and ambiguity but does not test runtime behavior.
When should another skill take over?
Use another skill for setup, asset downloads, command execution, paper lookup, or final reporting.

Developer Details

Author

lllllllama

License

MIT

Skillstore revision

r2

Version notice

The author did not declare a version.

Ref

656be3040aef5c047555a908cd5c695d22a4a548

Maintenance freshness

8/8/2026

Usage

15 downloads ยท 102 views

File structure

๐Ÿ“ agents/

๐Ÿ“„ openai.yaml

๐Ÿ“ references/

๐Ÿ“„ repo-scan-rules.md

๐Ÿ“ scripts/

๐Ÿ“„ extract_commands.py

๐Ÿ“„ scan_repo.py

๐Ÿ“„ SKILL.md