Enterprise DNAEnterprise DNA

Skills

repo-intake-and-plan

by lllllllama

README-first research reproduction skills with bounded execution, auditable evidence, and byte-preserving README annotations.

Our verdict

Not reviewed yet

We have not reviewed repo-intake-and-plan yet

No one at Enterprise DNA has checked this listing against its sources. The description comes from public listings gathered automatically. Any fact below shows where it came from and when it was last checked.

How we review records

From the listing

About repo-intake-and-plan

README-first research reproduction skills with bounded execution, auditable evidence, and byte-preserving README annotations.

Best for

Developers and researchers who need to reproduce and plan repository changes with strict documentation and evidence.

Use cases

  • Reproduce research findings from a repository's README to verify claims
  • Plan code changes with a structured, evidence-based intake process
  • Annotate READMEs without altering their original bytes for traceability

Notes

486 stars on GitHub. Last updated 2026-09-23. Licensed MIT.

Indexed from skills-sh. Verified against the live GitHub repo.

Pros

  • Bounded execution reduces risk of uncontrolled side effects
  • Auditable evidence supports verification and review
  • Byte-preserving annotations maintain original file integrity

Cons

  • Limited to README-first workflows, not general code analysis
  • Requires Python environment and setup
  • May not suit projects without detailed READMEs

Key facts

What we have checked

Days since the last commit
52
Checked GitHub
GitHub forks
20
Checked GitHub
GitHub stars
486
Checked GitHub
Installs
473.2K
Checked skills.sh
Open issues
1
Checked GitHub
Releases in the last 90 days
0
Checked GitHub

Each value shows when we last confirmed it and where it came from. Values we have not confirmed are left out, never guessed.

Stars and usage

How repo-intake-and-plan is growing

GitHub stars

486 to 486

stars. 1 Nov 2026 to 14 Nov 2026, 3 readings.

Source: GitHub. Checked .

Health and security

Is repo-intake-and-plan looked after, and what do its setup files show

Health score

47 out of 100

Does someone look after this repository? It does not say the code is good or safe. Worked out from GitHub signals checked . How it is worked out

PartPointsWhat we saw
Recent activity28 of 30Last push 52 days ago
Releases0 of 150 releases in 90 days
Issue repliesNot countedThe latest check has no issue response reading (fewer than 3 measured issues, or issues switched off)
Maintainer0 of 15Owned by a single user
Official sourceNot countedMCP servers only

Security check static checks

100 out of 100

Reads what is published about the server: package advisories, licence, secrets in the documented setup and tool permissions. Nothing is installed or run, so this is not a security assessment. Checked by edna-skill-static-v1 main@fb3ccdf5aa64. What it checks

  • Note No dependency list or install command was found in the skill, so there were no packages to look up on OSV.

Sources

Where this comes from

  • GitHubRegistry

    Checked · Days since the last commit, GitHub forks, GitHub stars, Open issues, Releases in the last 90 days

  • skills.shThird party

    Checked · Installs

A source shows what was published when we checked it. It does not certify security, performance or a working installation. Read our method.

Changelog

What changed

No changes recorded yet. Releases, price changes and deprecations appear here, with their dates, once we track them for this record.

Free 27-page guide

Get the free Developer’s Field Guide

A 27-page field guide to the AI coding workflow with Claude. Claude Code, MCP servers, the prompt patterns that work, and what to delegate. Free.

Enter your work email. We send it straight over, plus a few short notes worth knowing. Unsubscribe any time.

No spam. Unsubscribe any time.