Tracecat 仓库 同步
- 作者仓库星标 0
- 作者仓库 skills-registry
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
.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
<!-- tomevault:4.0:skill_md:2026-05-23 -->Source: adrojis/tracecat-skills — distributed by TomeVault.
- 流狐分类
- AI 智能
- 作者声明 Agent
- 未找到明确声明;不据此推断已兼容或已测试
- 静态检查
- 88 / 100 · 启发式扫描,不代表运行安全
- 作者 / 版本 / 许可
- @tomevault-io · 未声明 license
- 流狐 Token 估算
- 低消耗
- 流狐接入估算
- 即装即用
- 是否需要外部 API Key
- 未发现要求
- 检测到的系统要求
- 未声明
- 底层运行要求
- Python
- 检测到的文件与系统行为
-
- 只读
- 允许写入 / 修改
- 读取环境变量
- 检测到的网络行为
- 仅限本地
- 安装命令数
- 无(仅作为资料)
档案由构建时根据 SKILL.md 与安装命令自动衍生,可能与作者实际意图存在差异。
需要注意: 未限定 allowed-tools,默认拥有全部工具权限。
作者没有在当前 SKILL.md 中定义固定输出样例。 Component · Local Path · GitHub Repo MCP Server · <projectroot>/mcpserver/ · Owner's tracecat-mcp-community repo Skills · <projectroot>/tracecatskills/ · Owner's tracecat-skills repo
Sync Procedure
Compare local files with the GitHub repository to find what has changed.
Show the user what files will be pushed and what content has changed.
Use mcpmy-githubpushfiles or mcpmy-githubcreateorupdatefile to push changes.
Key files in the MCP server: Never sync: .env, nodemodules/, dist/, .env.local
# 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 |
… 作者原文负责流程事实;流狐只索引当前章节、要点、文件与命令。
章节 -> Repositories → Sync Procedure → 1. Identify changed files → 2. Review changes → 3. Push to GitHub → MCP Server Files to Sync
要点 -> 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
文件/命令 -> <projectroot>/mcpserver/ · tracecat-mcp-community · <projectroot>/tracecatskills/ · tracecat-skills · mcpmy-githubpushfiles · mcpmy-githubcreateorupdatefile · .env · nodemodules/
内容 SHA-256 -> b14c564181ce
原文结构
适用与边界
原文中的明确线索
<projectroot>/mcpserver/、tracecat-mcp-community、<projectroot>/tracecatskills/、tracecat-skills、mcpmy-githubpushfiles、mcpmy-githubcreateorupdatefile、.env、nodemodules/