agentsclimarketplace

Agent architect

Skill pngdeity/apm-user-repository/packages/agent-architect/.apm/skills/agent-architect

Personal APM marketplace — skills, prompts, agents, and instructions for AI coding agents

Install
npx -y skills add pngdeity/apm-user-repository --skill agent-architect

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

  • 0 stars0 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 author says it does

Copied from the file, not written here

Architect, write, structure, and maintain AI agent context files (AGENTS.md and SKILL.md). Use when creating new agent context configurations, scaffolding AGENTS.md files, designing SKILL.md modules, or determining where content belongs in the agent abstraction stack. Not for writing code or implementing features.

SKILL.md

3.3 KB, as published. Nobody here has run it

Agent Architect Skill

This skill governs the creation, structuring, and maintenance of AI agent context files. It enforces the "Abstraction Stack" model and provides a decision framework for determining correct file placement.

Abstraction Stack

Structure agent knowledge across two distinct layers to optimize token context and execution reliability:

  1. Foundation (AGENTS.md): Agent identity, global boundaries, and environment. Always active.
  2. Modules (SKILL.md): Specialized workflow recipes, loaded on demand via progressive disclosure.

Decision Heuristic

When documenting a process or configuring agent behavior, apply this logic to determine the correct output:

  1. Global constraint, architectural baseline, or repository-wide command? → Write it in AGENTS.md.
  2. Single, atomic function call (e.g., querying a database or an API)? → This is a Tool (a verb), not a context file. Suggest a code implementation. Consult the Google ADK and Microsoft Agent Framework sources (see references/knowledge-sources.md) to clarify the boundary between Tools and Skills.
  3. Specialized, multi-step workflow requiring reasoning? → This is a Skill (expertise). Create a new skill directory and write a SKILL.md file.
  4. Optimizing repository rules for a specific IDE or LLM? → Create a model-specific override file (e.g., CLAUDE.md, GEMINI.md) that inherits the spirit of AGENTS.md but translates formatting and tool-calling instructions into that model's optimal syntax.

Workflow: Creating Context Files

  1. Determine placement: Apply the Decision Heuristic above.
  2. Consult authoritative sources: Read references/file-specifications.md for required components of each file type (AGENTS.md, SKILL.md, model-specific overrides).
  3. Consult knowledge base: Read references/knowledge-sources.md for the canonical sources to consult based on the task at hand (agentskills.io specification, GitHub Copilot lessons, Google ADK, Microsoft Agent Framework, Anthropic guidance).
  4. Draft: Write the file with mandatory components and proper formatting.
  5. Validate: For SKILL.md, verify YAML frontmatter compliance against agentskills.io specification.

Verification

  1. Confirm the file type (AGENTS.md / SKILL.md / model override) matches the Decision Heuristic outcome.
  2. For SKILL.md: verify YAML frontmatter has name (kebab-case) and description (written as an API doc for the agent router).
  3. For AGENTS.md: verify it includes Persona, Tech Stack, Executable Commands, and Boundaries sections.
  4. For model-specific overrides: verify it translates, not duplicates, the AGENTS.md rules into model-appropriate syntax.

Keep looking

Skills are one crate of 328,083. 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.