tracecat-repo-sync

AI Community

Repo stars 0
Author repo skills-registry

Interpretation is structured for decision-making; original keeps the upstream SKILL.md unchanged.

Decide Fit First

Core job: Activate when user asks to sync, push, or publish local Tracecat MCP server code or Claude Code skills to their GitHub repositor…
Best fit: Use it when the task has reusable inputs, steps, and validation criteria rather than a one-off answer.
Avoid forcing it: If the source lacks commands, platform support, or external-service evidence, keep those fields unknown instead of guessing.

Design Intent

Structure: The skill is organized around “Repositories”, “Sync Procedure”, “1. Identify changed files”, “2. Review changes”, showing how the author expects the agent to judge fit, collect context, and produce verifiable output.
Trigger evidence: Prioritize the author’s wording around when to use it, what context to collect, and what output shape to produce.
Evidence boundary: Author text states facts, repository files prove commands and paths, and Fluxly only adds fit, limits, and usage judgment.

How To Use It

Inputs: Provide target material, scope, expected result, forbidden changes, and validation method.
Invocation: Name tracecat-repo-sync directly; if the source includes slash commands, start with the command and then add task context.
Validation: Start small and check whether the result follows “Repositories / Sync Procedure / 1. Identify changed files” before expanding.

Boundaries And Review

Dependencies: It usually needs no extra API key, so start with a small validation task.
Permissions: Declared permissions include read / write / env-read; ask the agent to state file, command, and rollback boundaries before acting.
Quality bar: A useful result names the deliverable, evidence, and next action. Generic prose means the task needs tighter context.

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

Never push .env files 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 main branch 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

tracecat-mcp-tools-expert — MCP tools reference

Reference Files

Source: adrojis/tracecat-skills — distributed by TomeVault.

Fluxly profile Author and license come from source; runtime, permissions, and network are Fluxly detections or estimates

Fluxly category: 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
Author / version / license: @tomevault-io · no license declared
Fluxly token estimate: Lean
Fluxly setup estimate: Plug-and-play
External API key: No requirement detected
Detected OS requirements: Unspecified
Runtime requirements: Python
Detected file/system behavior: Read-only
Write / modify
Env read
Detected network behavior: Local-only
Install commands: None (reference only)

Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.

Heads up: 未限定 allowed-tools，默认拥有全部工具权限。

Output preview tracecat-repo-sync.preview

The current SKILL.md does not define a fixed output example.

SKILL.md SKILL.md

# 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 |

…

Evidence boundary and execution chain

Author text anchors workflow facts; Fluxly only indexes current sections, terms, files, and commands.

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 -> <projectroot>/mcpserver/ · tracecat-mcp-community · <projectroot>/tracecatskills/ · tracecat-skills · mcpmy-githubpushfiles · mcpmy-githubcreateorupdatefile · .env · nodemodules/
body sha256 -> b14c564181ce