agent-config

Collect a Culture agent's system-prompt artifact, culture.yaml, and local skill inventory.

112|6|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/agentculture/culture --skill agent-config-agentculture
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-config
Source: https://github.com/agentculture/culture/tree/main/.claude/skills/agent-config
Command: npx skills add https://github.com/agentculture/culture --skill agent-config-agentculture

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires python3, pyyaml, and includes scripts (resource) components.

What problem does it solve?

This Skill solves the problem of not knowing exactly what a Culture agent is configured to do, by presenting the complete set of prompt-side and runtime-side artifacts plus the agent’s available local skills.

Core Features & Use Cases

  • Single-agent inventory view: Surfaces the detected system-prompt file (CLAUDE.md / AGENTS.md / GEMINI.md), the parallel culture.yaml, and the one-line list of .claude/skills/*/SKILL.md entries.
  • Backend-aware prompt detection: Detects the correct system-prompt filename using backend fingerprint rules, with a safe fallback to built-in prompt filenames when the registry is absent.
  • Path mode and suffix mode: Works either by pointing at a directory that contains the prompt file + culture.yaml, or by resolving an agent suffix via the Culture server manifest.
  • Read-only reporting: Provides configuration truth without judging alignment or drift, supporting operator onboarding and teaching workflows.

Quick Start

Ask: "Show agent <name>" (or run the script with a directory path) to get the agent’s prompt file, culture.yaml, and local skills index.

Frequently Asked Questions about agent-config

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I view an agent's complete configuration including system prompt and skills?

To view an agent's complete configuration, you can retrieve its system-prompt artifact, parallel culture.yaml, and locally registered skill inventory in a single read-only report by pointing to the agent's directory path or suffix.

What is agent configuration inventory and when do I need it?

Agent configuration inventory is a read-only report showing an agent's system-prompt file, culture.yaml, and local skills index. You need it during onboarding or teaching workflows to understand exactly what an agent is configured to do.

How does backend detection work for system prompt files like CLAUDE.md or AGENTS.md?

Backend detection for system prompt files uses backend-fingerprints.yaml rules to identify the correct filename, with a safe fallback to built-in prompt filenames like CLAUDE.md, AGENTS.md, or GEMINI.md when the registry is absent.

Can I resolve an agent configuration using a suffix instead of a directory path?

Yes, you can resolve an agent configuration using a suffix-resolved mode via the Culture server manifest, or you can use directory-path mode by pointing directly at a directory containing the prompt file and culture.yaml.

Do I need python3 and pyyaml to inventory agent configuration files?

Yes, you need python3 and pyyaml installed to run the inventory script that collects the system-prompt artifact, culture.yaml, and skill entries for read-only configuration reporting.

Does the agent configuration report check for alignment drift between prompt and runtime?

No, the agent configuration report provides configuration truth without judging alignment or drift, strictly performing read-only reporting of the system-prompt file, culture.yaml, and local skills index.