From Graph Sync Agent Kit
Technical implementation workflow for WordLift graph-sync projects. Use when editing or reviewing graph-sync project files, worai.toml profiles, mappings, static templates, postprocessor manifests, runtime behavior, troubleshooting, tests, docs/spec synchronization, or CI smoke contracts.
How this skill is triggered — by the user, by Claude, or both
Slash command
/graph-sync-agent-kit:graph-sync-projectThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use this skill for technical implementation work in WordLift graph-sync repositories. It covers runtime configuration, mappings, static templates, postprocessor behavior, troubleshooting, verification, and docs/spec synchronization.
Use this skill for technical implementation work in WordLift graph-sync repositories. It covers runtime configuration, mappings, static templates, postprocessor behavior, troubleshooting, verification, and docs/spec synchronization.
For semantic prioritization and cluster curation, use graph-sync-curator. For repo creation, commit, and push workflows, use graph-sync-repo-lifecycle.
Before editing:
Always load references/policy.md for policy-sensitive graph modeling or mapping work.
references/overview.md.references/cli-resolution.md.references/mappings.md.references/static-templates.md.references/postprocessors.md.references/troubleshooting.md.references/ci-checklist.md and consider graph-sync-github-workflow-review.graph-sync-postprocessor-authoring.graph-sync-yarrrml-review.When editing project files:
Use tiered validation. Prefer the project-documented validation command first.
Default checks when the project uses uv:
uv run pytest
When applicable, also run:
uv run ruff check .
Do not assume uv, pytest, or ruff are globally installed. If the default commands fail because the runner is unavailable, use the project-documented validation command, the active virtual environment, or ask before installing/fetching tooling.
If tests are absent or not meaningful, use a graph-sync CLI smoke check and the project-specific sync/audit path agreed with the user. Resolve the CLI through references/cli-resolution.md; do not assume bare worai is installed globally.
For graph-sync runtime changes, verify the affected behavior:
Summarize:
If work is tested and accepted, inspect git status. When project changes exist, explicitly ask whether to prepare a commit handoff through graph-sync-repo-lifecycle; if no project changes exist, say there is nothing to commit. Require explicit user confirmation before commits or remote pushes.
Guides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.
npx claudepluginhub wordlift/agent-marketplace --plugin graph-sync-agent-kit