القائمة
Git push to HTTPS remote using token authentication — avoids SSH setup, works in CI/automated environments.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
🧠 ontology-clawra v5.1 - Local Ontology Reasoning & Learning Engine **USE THIS SKILL WHENEVER** you need structured reasoning, knowledge graph management, logical inference, or learning from interactions. This is your go-to tool for: - Building and querying ontology knowledge graphs (concepts, entities, relationships) - Performing confidence-based reasoning with evidence tracking - Recording insights and patterns from completed tasks - Local memory search and knowledge retrieval **Key Use Cases:** - Before making complex decisions: "Let me use ontology-clawra to reason about this" - After completing tasks: "Record this learning to ontology-clawra" - Building domain expertise: "Create concepts for [domain] in ontology-clawra" - Analyzing patterns: "Query ontology-clawra for similar past cases" **Core Capabilities:** ✅ Local ontology storage in `~/.openclaw/skills/ontology-clawra/memory/` ✅ Confidence calculation (CONFIRMED/ASSUMED/SPECULATIVE) ✅ Learning from user confirmations ✅ Local memory search (no ne
Complete guide to using and extending Hermes Agent — CLI usage, setup, configuration, spawning additional agents, gateway platforms, skills, voice, tools, profiles, and a concise contributor reference. Load this skill when helping users configure Hermes, troubleshoot issues, spawn agent instances, or make code contributions.
从 GitHub 历史中彻底清除敏感文件的完整流程 — 使用 git filter-repo + force push，适用于清理意外提交的个人文件、工作文件等
清理 GitHub 历史和 ClawHub 中意外泄露的个人/工作文件
Configure WhatsApp and Telegram messaging platforms on Hermes Agent
Configure Telegram bot messaging channel for Hermes Agent, especially useful when behind Chinese firewall with SOCKS proxy
| name | git-https-push-with-token |
| description | Git push to HTTPS remote using token authentication — avoids SSH setup, works in CI/automated environments. |
| triggers | ["git push fails with \"authentication failed\"","HTTPS token embedded in URL but push still asks for credentials","git credential.helper interfering with URL-embedded auth"] |
Git push to an HTTPS remote fails even when the token is embedded in the URL:
remote: authentication failed
fatal: Authentication failed for 'https://github.com/user/repo.git'
Setting credential.helper overrides URL-embedded credentials.
Git's credential helper runs before the URL-embedded token is used. If credential.helper is configured, git uses that instead of the token in the URL.
# 1. Set remote URL with token embedded (no trailing spaces or special chars)
git remote set-url origin "https://github.com/USER/REPO.git"
# Actually embed token:
git remote set-url origin "https://GITHUB_TOKEN@github.com/USER/REPO.git"
# 2. CRITICAL: Remove/override any credential helper that would override URL token
git config --unset credential.helper # Remove global/default helper
# 3. Now push will use the URL-embedded token
git push origin main
# Store credentials in a file (note: writes token in plain text)
git config credential.helper "store --file ~/.git-credentials"
echo "https://GITHUB_TOKEN@github.com" > ~/.git-credentials
chmod 600 ~/.git-credentials
git push origin main
credential.helper is unset or points to a store that has the right credentialsgit remote -v shows the expected URL with token# See what git thinks the remote URL is
git remote -v
# See what credential helper is configured (global + local)
git config --list --show-origin | grep credential
# Test if credential helper is interfering
GIT_TRACE=1 git push origin main 2>&1 | grep -i credential