tracecat repo sync
- Repo stars 0
- Author repo skills-registry
- Domain
- AI
- Author-declared agents
- No explicit declaration found; this is not inferred or tested compatibility
- Static check
- 88 / 100 · heuristic scan, not runtime safety proof
- Runtime evidence
- Not run; no isolated runtime test evidence is currently recorded
- 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
- Detected file/system behavior
-
- Read-only
- Write / modify
- Env read
- Network behavior
- Local-only
- Install commands
- None (reference only)
Heads up: Tool permissions are not declared; actual access depends on the runtime.
# 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.md
```
## GitHub 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
1. **Never push `.env` files** or any file containing credentials
2. **Never push `.mcp.json`** — contains local paths and potentially sensitive env vars
3. **Always show diff** to user before pushing
4. **Use descriptive commit messages** summarizing changes
5. **Push to `main` branch** unless user specifies otherwise
6. **Check for existing files** first to get SHA (required for updates)
7. **Scan for local paths** before pushing — reject any file containing `C:\Users\`, `/home/`, or absolute local paths that would leak user info
8. **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
- [Common Mistakes](./COMMON_MISTAKES.md)
- [Examples](./EXAMPLES.md)
- [README](./README.md)
---
> Source: [adrojis/tracecat-skills](https://github.com/adrojis/tracecat-skills) — distributed by [TomeVault](https://tomevault.io).
<!-- tomevault:4.0:skill_md:2026-05-23 -->
Sections and files
Listed in source order.
sections -> Repositories → Sync Procedure → 1. Identify changed files → 2. Review changes → 3. Push to GitHub → MCP Server Files to Sync
terms -> Note · Never sync · Never push .env files · Never push .mcp.json · Always show diff · Use descriptive commit messages · Push to main branch · Check for existing files
files/cmd -> <project_root>/mcp_server/ · tracecat-mcp-community · <project_root>/tracecat_skills/ · tracecat-skills · mcp__my-github__push_files · mcp__my-github__create_or_update_file · .env · node_modules/
body sha256 -> b14c564181ce
Repositories
Component · Local Path · GitHub Repo MCP Server ·
<project_root>/mcp_server/· Owner'stracecat-mcp-communityrepo Skills ·<project_root>/tracecat_skills/· Owner'stracecat-skillsrepo Note: Local paths and GitHub owner are resolved at runtime from the working directory and git config.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_filesormcp__my-github__create_or_update_fileto push changes.MCP Server Files to Sync
Key files in the MCP server: Never sync:
.env,node_modules/,dist/,.env.local