algoforge-mcp-server/SKILL.md

name	description	metadata
algoforge-dev	Manage MQL5 Algo Forge code repositories. Use when the user asks to create a repo, commit or read MQL5 code, branch, open a pull request, file an issue, tag a release, or explore public projects on Algo Forge.	openclaw emoji requires 🔱 env ALGOFORGE_MCP_PATH

Algo Forge Dev Skill

This skill connects OpenClaw to MQL5 Algo Forge via a local MCP server. Use the Algo Forge MCP tools for all repository and version-control operations. Algo Forge is a Git platform, so the server works anywhere — it talks to the REST API over HTTPS.

Available Tools

Tool	Purpose
get_me	Confirm the connection and get the user's login (the repo owner)
list_repos	List the user's repositories
create_repo	Create a new repository
get_file	Read a file's content from a repo
commit_file	Create or update a file with a commit
list_branches	List branches in a repo
create_branch	Create a new branch
list_issues	List issues in a repo
create_issue	Open a new issue
open_pull_request	Open a PR from one branch into another
create_release	Tag a version with release notes
search_repos	Search public projects on Algo Forge

Workflow Rules

• Call get_me first — confirm the connection and use the returned login as the owner for the user's own repositories.
• Discover before creating — call list_repos before create_repo to avoid duplicating an existing project.
• Write clear commit messages — every commit_file call needs a message that describes the change, not a placeholder.
• Prefer branches and pull requests for changes — for anything beyond a trivial edit, create_branch, commit to it, then open_pull_request rather than committing straight to the default branch.
• Confirm before any write — summarize the action (repo, path, branch, message) and wait for the user to confirm before calling create_repo, commit_file, create_branch, open_pull_request, create_issue, or create_release.

Example Interactions

Create a project:

"Make a new repo for my grid EA and commit this code into it" → get_me → list_repos → confirm → create_repo → commit_file.

Review and fix:

"Read MyEA.mq5 and add a trailing stop" → get_file → propose the change → create_branch → commit_file → open_pull_request.

Ship a version:

"Tag this as version 1.0" → confirm → create_release with tag_name "v1.0".

Explore:

"Find public MQL5 grid trading projects" → search_repos with the query and summarize the results.

Safety Notes

• The token grants write access to the user's Algo Forge account. Always confirm before any create/commit/PR/release action.
• Never print or log the personal access token. The MCP server handles authentication.