tracecat-repo-sync
- Repo stars 0
- Author updated Live
- Author repo skills-registry
- Domain
- AI
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- Author / version / license
- @tomevault-io · no license declared
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- Python
- Permissions
-
- Read-only
- Write / modify
- Env read
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools，默认拥有全部工具权限。
---
name: tracecat-repo-sync
description: Activate when user asks to sync, push, or publish local Tracecat MCP server code or Claude Code…
category: ai
runtime: Python
---
# tracecat-repo-sync output preview
## PART A: Task fit
- Use case: Activate when user asks to sync, push, or publish local Tracecat MCP server code or Claude Code skills to their GitHub repositories Use when this capability is needed. You help synchronize local Tracecat MCP server code and skills to their GitHub repositories. runs entirely locally; runs on Python. Works with Claude Code, Cursor, Cline and 23 more..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Repositories / Sync Procedure / 1. Identify changed files” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Activate when user asks to sync, push, or publish local Tracecat MCP server code or Claude Code skills to their GitHub repositories Use when this capability is needed. You help synchronize local Tracecat MCP server code and skills to their GitHub repositories. runs entirely locally; runs on Python. Works with Claude Code, Cursor, Cline and 23 more.”.
- **02** When the source has headings, the agent prioritizes “Repositories / Sync Procedure / 1. Identify changed files” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files, read environment variables; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files, read environment variables; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. Choose the trigger
The source mentions slash commands such as `/home`; use them first when your agent supports command triggers.
Provide inputs and boundaries
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files, read environment variables.
Validate with a small run
Start with a small task and check whether the result follows “Repositories / Sync Procedure / 1. Identify changed files”. Inspect diffs, logs, previews, or tests before expanding scope.
Review before delivery
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: tracecat-repo-sync
description: Activate when user asks to sync, push, or publish local Tracecat MCP server code or Claude Code…
category: ai
source: tomevault-io/skills-registry
---
# tracecat-repo-sync
## When to use
- Activate when user asks to sync, push, or publish local Tracecat MCP server code or Claude Code skills to their GitHub…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Repositories / Sync Procedure / 1. Identify changed files” and keep inference separate from source facts.
- read files, write/modify files, read environment variables; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. Evidence boundary and execution chain
The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "tracecat-repo-sync" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Repositories / Sync Procedure / 1. Identify changed files
rules -> SKILL.md triggers / order / output contract
runtime -> Python | read files, write/modify files, read environment variables | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
}Tracecat Repository Sync
You help synchronize local Tracecat MCP server code and skills to their GitHub repositories.
Repositories
| Component | Local Path | GitHub Repo |
|---|---|---|
| MCP Server | <project_root>/mcp_server/ |
Owner's tracecat-mcp-community repo |
| Skills | <project_root>/tracecat_skills/ |
Owner's tracecat-skills repo |
Note: Local paths and GitHub owner are resolved at runtime from the working directory and git config.
Sync Procedure
1. Identify changed files
Compare local files with the GitHub repository to find what has changed.
2. Review changes
Show the user what files will be pushed and what content has changed.
3. Push to GitHub
Use mcp__my-github__push_files or mcp__my-github__create_or_update_file to push changes.
MCP Server Files to Sync
Key files in the MCP server:
mcp_server/
src/
index.ts # Entry point
client.ts # API client
tools.ts # MCP tool definitions
types.ts # TypeScript types
package.json
tsconfig.json
CLAUDE.md # Dev guide
.env # DO NOT SYNC (credentials)Never sync: .env, node_modules/, dist/, .env.local
Skills Files to Sync
tracecat_skills/
.claude-plugin/
plugin.json # Plugin manifest
skills/
tracecat-action-configuration/SKILL.md
tracecat-case-management/SKILL.md
tracecat-code-python/SKILL.md
tracecat-integration-expert/SKILL.md
tracecat-mcp-tools-expert/SKILL.md
tracecat-secrets-integrations/SKILL.md
tracecat-validation-debug/SKILL.md
tracecat-workflow-patterns/SKILL.md
tracecat-yaml-syntax/SKILL.md
tracecat-repo-sync/SKILL.mdGitHub MCP Tools
| Tool | Usage |
|---|---|
mcp__my-github__get_file_contents |
Read current file from GitHub |
mcp__my-github__create_or_update_file |
Create or update a single file (needs SHA for updates) |
mcp__my-github__push_files |
Push multiple files in a single commit |
mcp__my-github__list_commits |
Check latest commits |
Safety Rules
- Never push
.envfiles or any file containing credentials - Never push
.mcp.json— contains local paths and potentially sensitive env vars - Always show diff to user before pushing
- Use descriptive commit messages summarizing changes
- Push to
mainbranch unless user specifies otherwise - Check for existing files first to get SHA (required for updates)
- Scan for local paths before pushing — reject any file containing
C:\Users\,/home/, or absolute local paths that would leak user info - Scan for hardcoded credentials — reject any file containing passwords, API keys, or tokens in plain text
Related Skills
- tracecat-mcp-tools-expert — MCP tools reference
Reference Files
Source: adrojis/tracecat-skills — distributed by TomeVault.
Decide Fit First
Design Intent
How To Use It
Boundaries And Review