Agent Skills
› QuixiAI/Hexis
› self-inspection
self-inspection
GitHub用于审查 Hexis 源码及 PostgreSQL 实时数据库模式,通过 inspect_source 和 inspect_database_schema 工具定位代码与结构,对比基线与运行态差异,辅助缺陷诊断与实现验证。
Trigger Scenarios
询问系统实现细节
检查当前代码库状态
查看数据库实际结构
排查功能逻辑错误
Install
npx skills add QuixiAI/Hexis --skill self-inspection -g -y
SKILL.md
Frontmatter
{
"name": "self-inspection",
"aliases": [
"how",
"why",
"yourself",
"your",
"internals",
"schema",
"config",
"source",
"debug"
],
"category": "system",
"contexts": [
"heartbeat",
"chat"
],
"requires": {
"tools": [
"inspect_source",
"inspect_database_schema"
]
},
"bound_tools": [
"inspect_source",
"inspect_database_schema",
"inspect_config",
"review_recent_actions",
"review_recent_changes",
"self_repair"
],
"description": "Browse and search Hexis source code and inspect the live PostgreSQL database schema"
}
Self Inspection
Use this skill to answer questions about how Hexis is implemented, what the current checkout actually does, and what schema is running in PostgreSQL.
Evidence Order
- Inspect the source or live schema before making implementation claims.
- Use
inspect_sourceto locate and read the relevant code. Start withsearch, then read only the necessary line ranges. - Use
inspect_database_schemafor current database truth. Preferdescribe_relationorget_functionafter a narrowsearch. - Use the core-memory skill separately when prior decisions or experiences are relevant. Memory is historical evidence; source and live schema are implementation evidence.
- Reconcile differences explicitly. Baseline SQL files describe a fresh database, migrations evolve existing databases, and the live schema is the authority for what is running now.
Source Method
inspect_source(action="list", path="...", file_pattern="...")discovers repository files.inspect_source(action="search", query="...", path="...", file_pattern="...")finds definitions and call sites.inspect_source(action="read", path="...", offset=..., limit=...)reads a bounded, line-numbered range.- Follow references across modules when needed. Do not infer behavior from a filename or one isolated function.
Schema Method
- Start with
overviewonly when the relevant object is unknown. - Use
searchfor a table, column, view, or stored-function name fragment. - Use
describe_relationfor columns, defaults, constraints, indexes, and view definitions. - Use
get_functionto inspect the actual stored definition and overloads. - The schema tool is metadata-only and does not accept arbitrary SQL.
Reporting
- Distinguish facts observed in source, facts observed in the live schema, and inferences.
- Cite repository-relative paths and function/relation names.
- State when the running schema differs from baseline files or migrations.
- Use
review_recent_changesto see what changed about your own substrate — migrations, code rebuilds, prompt edits, and operator config decisions. - When tool calls, heartbeat steps, integrations, or memory retrieval have been
failing, use
self_repairto list unresolved defect reports, diagnose one with the source/schema evidence gathered here, and mark it resolved only after verification. It records and reasons about defects; it never silently edits source code. - Do not claim access to model weights, provider infrastructure, hardware, or secrets unless another explicit capability supplies that evidence.
- Do not expose credentials,
.envcontents, or unrelated private files.
Version History
-
97f625f
Current 2026-08-29 01:32
修复审批门控失效导致工具无授权执行的问题;优化技能可达性,增加别名支持以改善意图匹配;调整心跳路径默认可用工具集。
- 990da5f 2026-08-20 13:53


