菜单
WHAT: the CartON MCP — a persistent knowledge graph (Neo4j + ChromaDB) you add concepts to, query, edit, and project. WHEN: persisting knowledge, creating observations/concepts, querying concept networks, semantic search, or editing a concept's description/structured data.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/sancovp/carton-mcp --skill mcp-skill-carton命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
WHAT: the development-flow for the split-content capability — separating a concept whose description (n.d) holds raw CONTENT (a data dump / pasted document) from a real DESCRIPTION, by splitting the raw content into its own `{concept_name}_Desc_Content` node. Covers `carton_split_content.py` (both `build_split_spec`, the pure spec function, and `split_content_concept`, the thin neo4j-writing wrapper — self-contained, ONE module, per the one-capability-one-module law), the `Desc_Content` universal type, the `has_desc_content` relationship, and the `split_content_concept` MCP tool. WHEN: when editing `carton_split_content.py`, `split_content_concept`, the `Desc_Content` type, or the `has_desc_content` relationship; or adding a new capability that also needs the content-vs-description split (any of).
WHAT: the dev-flow for the OPTIONAL domain/subdomain/personal_domain/produces params on add_concept_tool_func — the internal chokepoint function every CartON concept-creation caller (Dragonbones, sm_gate.py, split_content_concept, the migration scripts) passes through, whether or not they use the add_concept MCP tool. WHEN: when editing add_concept_tool_func's domain/subdomain/personal_domain/produces params, merge_optional_domain_fields, or PERSONAL_DOMAINS in add_concept_tool.py (any of).
WHAT: the development-flow for changing the CartON KV / CartonObj capability — the embedded-structured-KV-in-concept-descriptions feature (a <CartonObj name=..>{ JSON-with-bare-refs }</CartonObj> fence in n.d): the carton_kv parser/normalizer, edit_carton_obj (surgical single-leaf body edits + remove_fence), validate_carton_obj (schema + did-you-mean refs), the auto_link_description fence-opacity, fence-preservation (carry_forward_fences), ref-expansion, and the is_schema schema registry. It is the COMPLETE distributed edit-set (lib ↔ utils wrappers ↔ MCP tools ↔ the linker ↔ the daemon's live parse path ↔ the schema graph) + deploy + the only valid E2E test. WHEN: when editing carton_kv.py, the edit_carton_obj / validate_carton_obj / get_concept-expand MCP tools, the auto_link_description fence-opacity masking, the daemon fence/desc-mode parse path (parse_queue_file_to_concepts / batch_create_concepts_neo4j), or the is_schema schema-registry; or adding ANY new CartonObj capability (any of).
基于 SOC 职业分类
正在显示 SKILL.md
| name | mcp-skill-carton |
| description | WHAT: the CartON MCP — a persistent knowledge graph (Neo4j + ChromaDB) you add concepts to, query, edit, and project. WHEN: persisting knowledge, creating observations/concepts, querying concept networks, semantic search, or editing a concept's description/structured data. |
MCP shim index for CartON (Cartographic Ontology Net) — a persistent knowledge graph on Neo4j (the
:Wiki namespace) + ChromaDB (semantic search). Saying a concept POSTs an add_event to SOMA :8091,
which validates and returns the verdict; CartON stores the result as a regioned KG.
add_concept — say/update a concept (is_a/part_of/instantiates/produces + has_*,
typed_values). desc_update_mode = append | prepend | replace | path | edit (surgical
str-replace via old_str_for_edit_case). stash/clear_stash for retry-merge.query_wiki_graph — read-only Cypher over :Wiki. get_concept / get_concept_network —
fetch one concept / its neighborhood. chroma_query — semantic search.edit_carton_obj / validate_carton_obj — edit/validate a <CartonObj> JSON fence inside a
concept's n.d (structured-data-in-description; see edit-carton-kv).set_properties / query_by_properties / remove_relationship — the property channel
(scratch-lane work-state; see the property-layer doctrine) + relationship deletion.add_observation_batch / observe_from_identity_pov — observation shapes (wrap add_concept).create_collection / add_to_collection / activate_collection / list_collections.substrate_projector — project a concept to a substrate (file / etc).ACCESS: via the carton MCP tools directly (mcp__carton__*), or through sancrev-treeshell GNOSYS nodes
(connect 'carton' first).
See reference.md for the full tool docs.