How do I install the Kramme:agents Md skill?

Run npx skillmds@latest add diegosouzapw/kramme-agents-md in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Kramme:agents Md safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: WARNING, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Kramme:agents Md?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Kramme:agents Md free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Kramme:agents Md?

diegosouzapw (@diegosouzapw) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Kramme:agents Md by diegosouzapw — Agent Skill

Name: Kramme:agents Md
Rating: 4.5 (4 reviews)
Author: diegosouzapw

Kramme:agents Md

This skill should be used when the user asks to "update AGENTS.md", "add to AGENTS.md", "maintain agent docs", or needs to add guidelines to agent instructions. Guides discovery of local skills and enforces structured, keyword-based documentation style.

diegosouzapw Updated Sep 8, 2026 54 repo stars

File contents

Adding to AGENTS.md

AGENTS.md is the canonical agent-facing documentation. Each rule should be minimal, but many rules are OK.

Before Writing

Discover local skills to reference:

find .claude/skills -name "SKILL.md" 2>/dev/null
ls plugins/*/skills/*/SKILL.md 2>/dev/null

Read each skill's frontmatter to understand when to reference it.

Guideline Keywords

Use these keywords to indicate requirement strength:

ALWAYS — Mandatory requirement
NEVER — Strong prohibition
PREFER — Strong recommendation, exceptions allowed
CAN — Optional, developer's discretion
NOTE — Context or clarification
EXAMPLE — Illustrative example

Strictness hierarchy: ALWAYS/NEVER > PREFER > CAN > NOTE/EXAMPLE

Writing Rules

Existing sections first - Only propose new sections if no appropriate existing section exists
One rule per bullet - Keep each guideline minimal and atomic
Start with keyword - Every rule begins with ALWAYS/NEVER/PREFER/CAN/NOTE
Headers + bullets - No paragraphs
Code blocks - For commands and templates
Reference, don't duplicate - Point to skills: "See .claude/skills/db-migrate/SKILL.md"
No filler - No intros, conclusions, or pleasantries

Common Sections

Add sections as needed for the project:

When Stuck

## When Stuck
- **ALWAYS** ask a clarifying question or propose alternatives
- **NEVER** initiate large speculative changes without confirmation

Git Commits

## Git Commits
- **ALWAYS** write succinct commit messages in imperative mood
- **ALWAYS** keep the first line short
- **NEVER** mention that you are an AI

Issue Management

## Linear Issues
- **NEVER** change issue status without explicit instruction
- **NEVER** create issues without explicit instruction

Package Manager

## Package Manager
Use **pnpm**: `pnpm install`, `pnpm dev`, `pnpm test`

Local Skills

Reference each discovered skill:

## Database
Use `db-migrate` skill. See `.claude/skills/db-migrate/SKILL.md`

Domain-Specific Sections

Add sections for each tech stack (Frontend, Backend, etc.) with domain-specific guidelines.

Anti-Patterns

Omit these:

"Welcome to..." or "This document explains..."
Obvious instructions ("run tests", "write clean code")
Explanations of why (just say what)
Long prose paragraphs
Content duplicated from skills (reference instead)

---name: kramme-agents-mddescription: This skill should be used when the user asks to "update AGENTS.md", "add to AGENTS.md", "maintain agent docs", or needs to add guidelines to agent instructions. Guides discovery of local skills and enforces structured, keyword-based documentation style.---# Adding to AGENTS.mdAGENTS.md is the canonical agent-facing documentation. Each rule should be minimal, but many rules are OK.## Before WritingDiscover local skills to reference:```bashfind .claude/skills -name "SKILL.md" 2>/dev/nullls plugins/*/skills/*/SKILL.md 2>/dev/null```Read each skill's frontmatter to understand when to reference it.## Guideline KeywordsUse these keywords to indicate requirement strength:- **ALWAYS** — Mandatory requirement- **NEVER** — Strong prohibition- **PREFER** — Strong recommendation, exceptions allowed- **CAN** — Optional, developer's discretion- **NOTE** — Context or clarification- **EXAMPLE** — Illustrative exampleStrictness hierarchy: ALWAYS/NEVER > PREFER > CAN > NOTE/EXAMPLE## Writing Rules- **Existing sections first** - Only propose new sections if no appropriate existing section exists- **One rule per bullet** - Keep each guideline minimal and atomic- **Start with keyword** - Every rule begins with ALWAYS/NEVER/PREFER/CAN/NOTE- **Headers + bullets** - No paragraphs- **Code blocks** - For commands and templates- **Reference, don't duplicate** - Point to skills: "See `.claude/skills/db-migrate/SKILL.md`"- **No filler** - No intros, conclusions, or pleasantries## Common SectionsAdd sections as needed for the project:### When Stuck```markdown## When Stuck- **ALWAYS** ask a clarifying question or propose alternatives- **NEVER** initiate large speculative changes without confirmation```### Git Commits```markdown## Git Commits- **ALWAYS** write succinct commit messages in imperative mood- **ALWAYS** keep the first line short- **NEVER** mention that you are an AI```### Issue Management```markdown## Linear Issues- **NEVER** change issue status without explicit instruction- **NEVER** create issues without explicit instruction```### Package Manager```markdown## Package ManagerUse **pnpm**: `pnpm install`, `pnpm dev`, `pnpm test````### Local SkillsReference each discovered skill:```markdown## DatabaseUse `db-migrate` skill. See `.claude/skills/db-migrate/SKILL.md````### Domain-Specific SectionsAdd sections for each tech stack (Frontend, Backend, etc.) with domain-specific guidelines.## Anti-PatternsOmit these:- "Welcome to..." or "This document explains..."- Obvious instructions ("run tests", "write clean code")- Explanations of why (just say what)- Long prose paragraphs- Content duplicated from skills (reference instead)

Frequently asked questions