agentsclimarketplace
Sign in

Project context bootstrap

Skill markoblogo/abvx-agent-skills/skills/project-context-bootstrap

Bootstrap usable project context before deep implementation work. Use when entering a new or unfamiliar repo, installing agent workflows into an existing codebase, auditing stale docs, or preparing a project for repeatable long-running agent work. Detect the stack, ask the user about the project, summarize understanding, propose compact context artifacts, and update only with approval.From its SKILL.md

Install
npx -y skills add markoblogo/abvx-agent-skills --skill project-context-bootstrap

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 14 stars14 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its file declares

Copied from the file, not written here

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

2.8 KB, 502 tokens by cl100k_base, as published. Nobody here has run it

Project Context Bootstrap

Create a compact, durable working model of a repo before the agent starts inventing one from guesswork.

Goal

Turn a repo with weak or missing agent-facing context into a repo with:

  • a clear stack and structure summary;
  • known commands and verification paths;
  • durable context files or notes with real content;
  • explicit approval before reorganizing existing docs.

Workflow

  1. Detect
    • inspect project manifests, lockfiles, workspace layout, test commands, and major directories;
    • detect whether context already exists: AGENTS.md, docs/ai/, runbooks, plans, or other agent-facing docs.
  2. Study existing context first
    • if the repo already has useful docs, read them before proposing replacements;
    • separate what looks good, stale, missing, or conflicting.
  3. Ask
    • have a real project-discovery conversation with the user;
    • cover what the product is, who uses it, main features, risky areas, workflow conventions, and external dependencies;
    • follow up until the project is actually understandable.
  4. Summarize
    • restate your understanding in concise project language;
    • confirm accuracy before writing or reorganizing context.
  5. Propose
    • suggest the smallest useful context structure:
      • top-level AGENTS.md or compact startup doc;
      • docs/ai/architecture.md;
      • docs/ai/how-to-test.md;
      • task-specific notes only if needed;
    • ask before reorganizing or overwriting anything durable.
  6. Populate
    • write real content from code and user input, not placeholders;
    • include concrete commands, file paths, key modules, and current conventions.
  7. Validate
    • verify the new context is small, accurate, and actually useful for the next session.

Existing Repo Rules

  • Preserve good context; do not replace it with generic scans.
  • Show what you want to keep, improve, and add before changing layout.
  • Never silently move or delete user-written docs.

Compression Rules

  • Keep startup context compact.
  • Put deeper material behind explicit paths.
  • Prefer one good entrypoint per topic instead of many tiny fragmented notes.

Final Report

Include what was detected, what was confirmed by the user, what context was added or updated, and what should be read first in the next session.

What ships with it: 2 files

1.7 KB alongside SKILL.md

agents/

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.