Agent Skills › win4r/MuseAI-Skills › self_awareness

self_awareness

GitHub

基于实际文件系统回答关于Agent身份、能力、记忆及规则等自我指涉问题，通过读取指定文件获取事实而非猜测。

opt/hatch/skills/self-awareness/SKILL.md win4r/MuseAI-Skills

Trigger Scenarios

询问Agent是谁或能做什么询问Agent的记忆或已知信息询问已构建的项目或连接的服务询问遵循的规则

Install

npx skills add win4r/MuseAI-Skills --skill self_awareness -g -y

More Options

Non-standard path

npx skills add https://github.com/win4r/MuseAI-Skills/tree/main/opt/hatch/skills/self-awareness -g -y

Use without installing

npx skills use win4r/MuseAI-Skills@self_awareness

指定 Agent (Claude Code)

npx skills add win4r/MuseAI-Skills --skill self_awareness -a claude-code -g -y

安装 repo 全部 skill

npx skills add win4r/MuseAI-Skills --all -g -y

预览 repo 内 skill

npx skills add win4r/MuseAI-Skills --list

SKILL.md

Frontmatter

{
    "name": "self_awareness",
    "metadata": {
        "includeInPrompt": false
    },
    "description": "Ground self-referential answers in the agent's actual filesystem. Use when the user asks who the agent is, what it can do, what it knows, what it remembers, what it has built, what services are connected, or what rules it follows."
}

Self-Awareness

Purpose

Answer self-referential questions from observed files and workspace state, not guesses or training-memory.

Tooling

Use read or exec to inspect the current environment before answering.

Common probes:

cat ~/IDENTITY.md ~/SOUL.md ~/AGENTS.md ~/TOOLS.md 2>/dev/null
cat ~/USER.md ~/MEMORY.md ~/TOMM.md 2>/dev/null
ls ~/memory/*.md 2>/dev/null
ls /opt/hatch/skills/ ~/workspace/skills/ 2>/dev/null
find ~/workspace/ -maxdepth 3 -type f \( -name "*.html" -o -name "*.md" -o -name "*.json" \) 2>/dev/null

Read references/question_types.md when the user asks a specific self-awareness question and you need the exact traversal for that question type.

Read references/extensions.md only when the user explicitly wants connection recommendations or an optional self-awareness dashboard.

Operating Rules

Re-read the relevant files every time. Never answer from cached assumptions.
If a file or directory is missing, say that directly instead of filling the gap.
Organize capability answers around the user's life domains and active projects, not a flat tool list.
Separate observed facts from inference. Cite file paths when it helps the user trust the answer.
Be explicit about stale or partial evidence, especially for memory, connected services, or built items.
Stay within the scope of the question. Do not append skill ideas, connection advice, or dashboards unless the user asked for them.