Agent skill

init

Create an AGENTS.md contributor guide for a repository (or a subdirectory) following a concise, repo-specific template. Use when the user runs /init.

Stars 78
Forks 21

Install this agent skill to your Project

npx add-skill https://github.com/OpenHands/extensions/tree/main/skills/init

SKILL.md

Initialize AGENTS.md

Use this skill when the user asks to scaffold an AGENTS.md file (project guidelines for AI agents) for the current repository.

Target path rules

  • /init: create AGENTS.md at the repository root.
  • /init <path>: create AGENTS.md scoped to <path>.
    • If <path> is a directory, write <path>/AGENTS.md.
    • If <path> ends with .md, treat it as the full output file path.

Never overwrite an existing file silently. If the target file already exists, ask the user whether to (a) keep it, (b) edit it, or (c) replace it.

Workflow

  1. Inspect the repo to tailor the guide

    • Skim top-level structure (ls, find -maxdepth 2).
    • Read the primary docs (README*, CONTRIBUTING*, DEVELOPMENT*, Makefile).
    • Identify build tooling and common commands (pyproject.toml, package.json, CI configs).
    • Locate tests and how they are run (tests/, workflow YAMLs, task runners).
  2. Write a concise AGENTS.md using the spec below.

  3. Create the file at the target location.

AGENTS.md spec (inspired by Codex /init)

  • Title the document: # Repository Guidelines.
  • Use Markdown headings (##) to organize sections.
  • Keep it concise: 200–400 words.
  • Keep explanations short, direct, and specific to the repo.
  • Prefer concrete examples (commands, directory paths, naming patterns).

Recommended sections (adapt as needed)

  • Project Structure & Module Organization
  • Build, Test, and Development Commands
  • Coding Style & Naming Conventions
  • Testing Guidelines
  • Commit & Pull Request Guidelines
  • Optional: Security & Configuration Tips, Architecture Overview, Agent-specific instructions

Content guidelines

  • Only include information that’s broadly useful for future tasks (avoid one-off issue details).
  • If the repo already contains nested AGENTS.md files, briefly mention that more deeply nested files override broader ones within their directory tree.

Expand your agent's capabilities with these related and highly-rated skills.

OpenHands/extensions

releasenotes

Generate formatted changelogs from git history since the last release tag. Use when preparing release notes that categorize changes into breaking changes, features, fixes, and other sections.

78 21
Explore
OpenHands/extensions

bitbucket

Interact with Bitbucket repositories and pull requests using the BITBUCKET_TOKEN environment variable. Use when working with code hosted on Bitbucket or managing Bitbucket resources via API.

78 21
Explore
OpenHands/extensions

add-skill

Add an external skill from a GitHub repository to the current workspace. Use when users want to import, install, or add a skill from a GitHub URL (e.g., `/add-skill https://github.com/OpenHands/extensions/tree/main/skills/codereview` or "add the codereview skill from https://github.com/OpenHands/extensions/"). Handles fetching the skill files and placing them in .agents/skills/.

78 21
Explore
OpenHands/extensions

add-javadoc

Add comprehensive JavaDoc documentation to Java classes and methods. Use when documenting Java code, adding API documentation, or improving code documentation.

78 21
Explore
OpenHands/extensions

flarglebargle

A test skill that responds to the magic word "flarglebargle" with a compliment. Use for testing skill activation and trigger functionality.

78 21
Explore
OpenHands/extensions

codereview-roasted

Brutally honest code review in the style of Linus Torvalds, focusing on data structures, simplicity, and pragmatism. Use when you want critical, no-nonsense feedback that prioritizes engineering fundamentals over style preferences.

78 21
Explore

Didn't find tool you were looking for?

Be as detailed as possible for better results