Capture Conversation
outline/outline
Save the current conversation, a decision, or a set of notes as a document in an Outline collection; use when the user wants to keep what was discussed in their knowledge base.
A skill your agent uses whenever an APS (production scheduling) agent needs to interact with a local filesystem-based knowledge base.
$ npx skills add LeoYeAI/openclaw-master-skills --skill aps-filesystem-agent -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills aps-filesystem-agent --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/aps-filesystem-agent .claude/skills/aps-filesystem-agent && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "aps-filesystem-agent" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/aps-filesystem-agent into .claude/skills/aps-filesystem-agent/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "aps-filesystem-agent", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/aps-filesystem-agentType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add LeoYeAI/openclaw-master-skills --skill aps-filesystem-agent -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills aps-filesystem-agent --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/aps-filesystem-agent .agents/skills/aps-filesystem-agent && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "aps-filesystem-agent" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/aps-filesystem-agent into .agents/skills/aps-filesystem-agent/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "aps-filesystem-agent", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add LeoYeAI/openclaw-master-skills --skill aps-filesystem-agent -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills aps-filesystem-agent --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/aps-filesystem-agent .cursor/skills/aps-filesystem-agent && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "aps-filesystem-agent" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/aps-filesystem-agent into .cursor/skills/aps-filesystem-agent/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "aps-filesystem-agent", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/LeoYeAI/openclaw-master-skills.git --path skills/aps-filesystem-agent--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add LeoYeAI/openclaw-master-skills --skill aps-filesystem-agent -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills aps-filesystem-agent --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/aps-filesystem-agent .gemini/skills/aps-filesystem-agent && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "aps-filesystem-agent" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/aps-filesystem-agent into .gemini/skills/aps-filesystem-agent/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "aps-filesystem-agent", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install LeoYeAI/openclaw-master-skills aps-filesystem-agentInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add LeoYeAI/openclaw-master-skills --skill aps-filesystem-agent -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/aps-filesystem-agent .github/skills/aps-filesystem-agent && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "aps-filesystem-agent" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/aps-filesystem-agent into .github/skills/aps-filesystem-agent/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "aps-filesystem-agent", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add LeoYeAI/openclaw-master-skills --skill aps-filesystem-agent -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills aps-filesystem-agent --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/aps-filesystem-agent .opencode/skills/aps-filesystem-agent && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "aps-filesystem-agent" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/aps-filesystem-agent into .opencode/skills/aps-filesystem-agent/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "aps-filesystem-agent", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
aps-filesystem-agentA skill your agent uses whenever an APS (production scheduling) agent needs to interact with a local filesystem-based knowledge base.
Aps Filesystem Agent is an agent skill from LeoYeAI/openclaw-master-skills. Use this skill whenever an APS (production scheduling) agent needs to interact with a local filesystem-based knowledge base. Triggers include: reading or searching APS rules, loading client memory or shop floor configurations, proposing new rules to the knowledge base, updating or deprecating existing knowledge, querying decision history, rebuilding the vector index, or any task involving the apsknowledgebase/ directory structure. Also use when the agent needs to understand what knowledge is available before…
Its SKILL.md is about 4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `_meta.json`, `references/schemas.md` and `references/scripts.md`).
It sits in Knowledge Management, covering Knowledge bases. The repository describes itself as: 🧠 Curated collection of 1209+ best OpenClaw skills — weekly updated by MyClaw.ai. The licence is MIT.
6 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit e5199b5. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
gitpythonFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Aps Filesystem Agent loads about 4k tokens when it runs, and up to ~7.2k if it reads all its reference files. Until then it costs about 184 tokens; SKILL.md has 529 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from LeoYeAI/openclaw-master-skills at commit e5199b5, republished under its MIT licence (© LeoYeAI). 529 words, ~4,017 tokens.
.claude/skills/aps-filesystem-agent/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.This skill teaches an APS scheduling agent how to navigate, query, and maintain a local filesystem-based knowledge base. The filesystem is the single source of truth for all domain rules, client memory, and problem schemas. A vector index sits on top for semantic retrieval, and Git tracks every change for auditability.
aps_knowledge_base/
├── .git/ ← version history, never touch manually
├── domain_rules/ ← APS rules extracted from conversations
│ ├── _index.json ← master rule registry (always update this)
│ ├── machine_rules/
│ ├── operator_rules/
│ └── material_rules/
├── client_memory/ ← persistent understanding of this customer
│ ├── _profile.json ← shop floor + planning process + preferences
│ ├── shop_floor/
│ ├── planning_process/
│ └── decision_history/ ← one file per scheduling session
├── problem_schemas/ ← modeling templates by problem type
├── solver_configs/ ← solver parameters and routing thresholds
├── pending_review/ ← proposed knowledge awaiting human approval
└── logs/
├── decisions/ ← audit trail of scheduling decisions
└── knowledge_changes/ ← audit trail of knowledge writesBefore doing anything, confirm the knowledge base root exists:
ls aps_knowledge_base/ 2>/dev/null || echo "Knowledge base not initialized"If it doesn't exist yet, initialize it (see "Initializing a new knowledge base" below).
Always load the client profile first — it tells you the shop floor topology, planning process, and output preferences that frame every other decision.
import json, pathlib
kb = pathlib.Path("aps_knowledge_base")
profile = json.loads((kb / "client_memory/_profile.json").read_text())
shop = profile["shop_floor"] # type, stages, machines_per_stage, etc.
prefs = profile["preferences"] # primary_objective, output_format, etc.Use semantic search when you know what you need but not which file has it. This requires the vector index to be built (see "Maintaining the vector index").
import chromadb
client = chromadb.PersistentClient(path="aps_knowledge_base/.chromadb")
collection = client.get_collection("domain_rules")
results = collection.query(
query_texts=["operator HSE certification machine maintenance"],
n_results=5,
where={"status": "active"} # only retrieve active rules
)
# results["ids"], results["documents"], results["metadatas"]
for doc, meta in zip(results["documents"][0], results["metadatas"][0]):
print(f"[{meta['rule_id']}] {meta['name']}: {doc}")When you already know the rule ID (e.g., from a decision log):
rule_path = kb / f"domain_rules/{category}/{rule_id}.json"
rule = json.loads(rule_path.read_text())Inject the Top-K most relevant rules into the scheduling context:
def get_relevant_rules(query: str, top_k: int = 5) -> list[dict]:
collection = client.get_collection("domain_rules")
results = collection.query(
query_texts=[query],
n_results=top_k,
where={"status": "active"}
)
rules = []
for rule_id, meta in zip(results["ids"][0], results["metadatas"][0]):
path = kb / meta["file_path"]
rules.append(json.loads(path.read_text()))
return rulesproblem_type = "flow_shop" # or job_shop, rcpsp, re_entrant
schema = json.loads((kb / f"problem_schemas/{problem_type}.json").read_text())history_dir = kb / "client_memory/decision_history"
sessions = sorted(history_dir.glob("session_*.json"), reverse=True)
last_session = json.loads(sessions[0].read_text()) if sessions else {}The agent NEVER writes directly to the main knowledge directories.
All new knowledge goes to pending_review/ first, then a human confirms.
Call this whenever you extract a new constraint or rule from a conversation:
import json, pathlib, datetime
def propose_rule(rule_content: dict, source_quote: str, session_id: str):
kb = pathlib.Path("aps_knowledge_base")
pending = kb / "pending_review"
pending.mkdir(exist_ok=True)
ts = datetime.datetime.utcnow().strftime("%Y%m%d_%H%M%S")
proposal = {
**rule_content,
"status": "proposed",
"metadata": {
**rule_content.get("metadata", {}),
"created_at": datetime.datetime.utcnow().isoformat() + "Z",
"created_by": "ai_agent",
"confirmed_by": None,
"source_session": session_id,
"source_quote": source_quote,
"use_count": 0,
"confidence": 0.9
}
}
out_path = pending / f"proposed_{rule_content['id']}_{ts}.json"
out_path.write_text(json.dumps(proposal, ensure_ascii=False, indent=2))
# Return the summary to show the user for confirmation
return {
"proposal_file": str(out_path),
"rule_id": rule_content["id"],
"name": rule_content["name"],
"description": rule_content["description"]
}After calling this, always present the proposal to the user with a confirmation prompt before moving on. Format it like this:
建议将以下内容加入知识库:
规则ID: {rule_id}
名称: {name}
描述: {description}
来源: "{source_quote}"
[确认入库] [修改后入库] [忽略本次]Wait for explicit confirmation before proceeding to confirm_proposal().
def propose_memory_update(memory_type: str, updates: dict, reason: str):
"""
memory_type: 'shop_floor' | 'planning_process' | 'preferences'
"""
pending = kb / "pending_review"
ts = datetime.datetime.utcnow().strftime("%Y%m%d_%H%M%S")
proposal = {
"type": "client_memory_update",
"memory_type": memory_type,
"updates": updates,
"reason": reason,
"proposed_at": datetime.datetime.utcnow().isoformat() + "Z"
}
out_path = pending / f"proposed_memory_{memory_type}_{ts}.json"
out_path.write_text(json.dumps(proposal, ensure_ascii=False, indent=2))
return str(out_path)Only call these functions after the user has explicitly confirmed in chat.
def confirm_proposal(proposal_file: str, confirmed_by: str):
"""Move a proposal from pending_review into the live knowledge base."""
kb = pathlib.Path("aps_knowledge_base")
proposal_path = pathlib.Path(proposal_file)
proposal = json.loads(proposal_path.read_text())
if proposal.get("type") == "client_memory_update":
_apply_memory_update(proposal, confirmed_by)
else:
_apply_rule(proposal, confirmed_by)
# Remove from pending
proposal_path.unlink()
# Update vector index and commit
_update_vector_index(proposal)
_git_commit(proposal, confirmed_by)
def _apply_rule(proposal: dict, confirmed_by: str):
rule_type = proposal.get("type", "general")
category_map = {
"machine_constraint": "machine_rules",
"operator_constraint": "operator_rules",
"material_constraint": "material_rules",
}
subdir = category_map.get(rule_type, "machine_rules")
dest = kb / f"domain_rules/{subdir}/{proposal['id']}.json"
dest.parent.mkdir(parents=True, exist_ok=True)
proposal["status"] = "active"
proposal["metadata"]["confirmed_by"] = confirmed_by
proposal["metadata"]["confirmed_at"] = (
datetime.datetime.utcnow().isoformat() + "Z"
)
dest.write_text(json.dumps(proposal, ensure_ascii=False, indent=2))
# Refresh the index file
_refresh_rule_index()
def _apply_memory_update(proposal: dict, confirmed_by: str):
profile_path = kb / "client_memory/_profile.json"
profile = json.loads(profile_path.read_text())
memory_type = proposal["memory_type"]
if memory_type not in profile:
profile[memory_type] = {}
profile[memory_type].update(proposal["updates"])
profile["last_updated"] = datetime.datetime.utcnow().isoformat() + "Z"
profile_path.write_text(json.dumps(profile, ensure_ascii=False, indent=2))The vector index must stay in sync with the filesystem. Rebuild it whenever rules are added, updated, or deprecated.
def _update_vector_index(rule: dict):
import chromadb
client = chromadb.PersistentClient(path="aps_knowledge_base/.chromadb")
try:
collection = client.get_or_create_collection("domain_rules")
except Exception:
collection = client.create_collection("domain_rules")
text = f"{rule['name']} {rule['description']} {' '.join(rule.get('metadata', {}).get('tags', []))}"
meta = {
"rule_id": rule["id"],
"name": rule["name"],
"status": rule.get("status", "active"),
"constraint_type": rule.get("constraint_type", "soft"),
"file_path": f"domain_rules/{_infer_subdir(rule)}/{rule['id']}.json"
}
collection.upsert(ids=[rule["id"]], documents=[text], metadatas=[meta])python aps_knowledge_base/scripts/rebuild_index.pySee references/scripts.md for the full rebuild script content.
Every confirmed knowledge change gets a Git commit automatically.
import subprocess
def _git_commit(item: dict, confirmed_by: str):
kb_path = "aps_knowledge_base"
item_id = item.get("id", item.get("memory_type", "unknown"))
item_type = item.get("type", "update")
action = "add" if item.get("status") == "active" else "update"
msg = f"{action}: {item_id} {item_type} ({confirmed_by})"
subprocess.run(["git", "-C", kb_path, "add", "-A"], check=True)
subprocess.run(["git", "-C", kb_path, "commit", "-m", msg], check=True)Commit message conventions:
add: rule_003 operator_constraint (big_boss)
update: client_memory shop_floor topology (plant_manager)
deprecate: rule_002 machine_a3 calibration - operator left (admin)
restore: rule_002 machine_a3 calibration (admin)To view history for a specific rule:
git -C aps_knowledge_base log --oneline -- domain_rules/operator_rules/rule_003.jsondef deprecate_rule(rule_id: str, reason: str, deprecated_by: str):
# find the file
for f in (kb / "domain_rules").rglob(f"{rule_id}.json"):
rule = json.loads(f.read_text())
rule["status"] = "deprecated"
rule["metadata"]["deprecated_at"] = datetime.datetime.utcnow().isoformat() + "Z"
rule["metadata"]["deprecation_reason"] = reason
f.write_text(json.dumps(rule, ensure_ascii=False, indent=2))
# remove from vector index so it won't be retrieved
client = chromadb.PersistentClient(path="aps_knowledge_base/.chromadb")
col = client.get_collection("domain_rules")
col.update(ids=[rule_id], metadatas=[{**col.get(ids=[rule_id])["metadatas"][0], "status": "deprecated"}])
_git_commit({"id": rule_id, "type": "deprecation"}, deprecated_by)
_refresh_rule_index()
return True
return FalseAfter every scheduling session, persist the decision for future reference:
def log_decision(session_id: str, decision: dict, rules_used: list[str]):
log_entry = {
"session_id": session_id,
"timestamp": datetime.datetime.utcnow().isoformat() + "Z",
"decision_summary": decision,
"triggered_by_rules": rules_used,
"human_confirmed": True
}
log_path = kb / f"client_memory/decision_history/{session_id}.json"
log_path.write_text(json.dumps(log_entry, ensure_ascii=False, indent=2))
# Also bump use_count on every rule that was triggered
for rule_id in rules_used:
_increment_use_count(rule_id)Run these checks periodically or before a major scheduling session.
def check_knowledge_health() -> dict:
issues = []
profile = json.loads((kb / "client_memory/_profile.json").read_text())
# Check for rules referencing people/machines that no longer exist
known_operators = profile.get("operators", {}).get("active", [])
for f in (kb / "domain_rules").rglob("*.json"):
rule = json.loads(f.read_text())
if rule.get("status") != "active":
continue
for op in rule.get("scope", {}).get("operators", []):
if op not in known_operators:
issues.append({
"rule_id": rule["id"],
"issue": f"references operator '{op}' not in active roster"
})
# Flag rules unused for 180+ days
cutoff = datetime.datetime.utcnow() - datetime.timedelta(days=180)
for f in (kb / "domain_rules").rglob("*.json"):
rule = json.loads(f.read_text())
if rule.get("status") != "active":
continue
last_used = rule.get("metadata", {}).get("last_used_at")
if last_used and datetime.datetime.fromisoformat(last_used[:-1]) < cutoff:
issues.append({
"rule_id": rule["id"],
"issue": "not used in 180+ days — consider deprecating"
})
return {"issues": issues, "checked_at": datetime.datetime.utcnow().isoformat()}If aps_knowledge_base/ does not exist, bootstrap it:
mkdir -p aps_knowledge_base/{domain_rules/{machine_rules,operator_rules,material_rules},client_memory/{shop_floor,planning_process,decision_history},problem_schemas,solver_configs,pending_review,logs/{decisions,knowledge_changes},.chromadb}
cd aps_knowledge_base && git init && git commit --allow-empty -m "init: knowledge base"Then create client_memory/_profile.json with the shell structure and fill it
in from the conversation (use propose_memory_update + confirmation flow).
See references/schemas.md for the full JSON schemas for every file type.
client_memory/_profile.json — confirm shop floor topology is currentpending_review/ — if any proposals await, surface them to the userproblem_schemas/<type>.json templatelog_decision() with the rules that were triggeredpropose_rule() and await confirmationFor detailed schemas and the rebuild script, read these when needed:
references/schemas.md — full JSON schemas for rules, client memory, proposalsreferences/scripts.md — rebuild_index.py full source code© LeoYeAI, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 3 other files (references) in skills/aps-filesystem-agent of LeoYeAI/openclaw-master-skills.
Open the folder on GitHubat commit e5199b5
Aps Filesystem Agent next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Aps Filesystem Agent this skillLeoYeAI/openclaw-master-skills | 2.2k | — | ~4k | Automated safety check: Pass | MIT | |
| Capture Conversationoutline/outline | 41k | — | ~474 | Automated safety check: Pass | Custom licence | |
| Project CairniBlinkQ/project-cairn | 235 | 2 repos | ~861 | Automated safety check: Pass | MIT | |
| LLM Wiki Knowledge GraphEgonex-AI/Understand-Anything | 86k | 1 repos | ~1.5k | Automated safety check: Pass | MIT | |
| Find And Citeoutline/outline | 41k | — | ~537 | Automated safety check: Pass | Custom licence | |
| Xhs Virtual Productchenjin-cmd/xhs-virtual-product | 727 | — | ~862 | Automated safety check: Pass | MIT |
outline/outline
Save the current conversation, a decision, or a set of notes as a document in an Outline collection; use when the user wants to keep what was discussed in their knowledge base.
iBlinkQ/project-cairn
Standardize how an AI-collaboration project turns work into reusable knowledge.
Egonex-AI/Understand-Anything
Detects a Karpathy-pattern LLM wiki and builds an interactive knowledge graph with entities, implicit relationships and topic clusters.
outline/outline
Answer questions from the Outline knowledge base with quotes and links to the source documents; use when the user asks what the team knows, documented, or decided about a topic.
chenjin-cmd/xhs-virtual-product
This skill helps plan, select, produce, and market Xiaohongshu (RED) virtual/digital products — templates, knowledge bases, test tools, study materials.
VectifyAI/OpenKB
A skill your agent uses when the user asks about content in their OpenKB knowledge base — research topics, concepts compiled from their documents, cross-document synthesis — or mentions openkb, an…
LeoYeAI/openclaw-master-skills
Manages pipelines on a DevOps quality and efficiency platform through its OpenAPI: list workspaces and templates, create, update, run and cancel pipelines, and read run records.
LeoYeAI/openclaw-master-skills
Patches OpenClaw's Feishu extension so an edited document triggers an isolated agent session that reads the doc and replies inline, turning it into a live chat space.
LeoYeAI/openclaw-master-skills
Multi-context memory management system for OpenClaw agents with group-isolated storage, global shared memory, workspace organization, and group-specific skills isolation.
LeoYeAI/openclaw-master-skills
Runs a brand's AI-search visibility work end to end: diagnosing how AI platforms represent it, repositioning it, producing AI-optimized content and monitoring ongoing mentions.
LeoYeAI/openclaw-master-skills
Installs and authenticates the gws CLI, then automates Gmail, Drive, Sheets, Calendar, Docs, Chat and Tasks with ready-made recipes, persona bundles and security audits.
LeoYeAI/openclaw-master-skills
Runs four advisor roles, a fitness coach, nutritionist, data analyst and TCM practitioner, to build a health profile and track workouts, diet and wellness over time.
Categories
A skill your agent uses whenever an APS (production scheduling) agent needs to interact with a local filesystem-based knowledge base. Aps Filesystem Agent is an agent skill from LeoYeAI/openclaw-master-skills. Use this skill whenever an APS (production scheduling) agent needs to interact with a local filesystem-based knowledge base.
Aps Filesystem Agent fits situations like: an APS (production scheduling) agent needs to interact with a local filesystem-based knowledge base; include: reading; searching APS rules; loading client memory.
Run `npx skills add LeoYeAI/openclaw-master-skills --skill aps-filesystem-agent -a claude-code`. Or copy the skill folder (skills/aps-filesystem-agent in LeoYeAI/openclaw-master-skills) into .claude/skills/aps-filesystem-agent in your project. Claude Code loads it when a task matches its description.
Run `npx skills add LeoYeAI/openclaw-master-skills --skill aps-filesystem-agent -a codex`. Or copy the skill folder (skills/aps-filesystem-agent in LeoYeAI/openclaw-master-skills) into .agents/skills/aps-filesystem-agent in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add LeoYeAI/openclaw-master-skills --skill aps-filesystem-agent -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/aps-filesystem-agent, .gemini/skills/aps-filesystem-agent, .github/skills/aps-filesystem-agent and .opencode/skills/aps-filesystem-agent in your project.
Going by SKILL.md and its folder, Aps Filesystem Agent needs the command-line tools its instructions call (git and python). Our summary lists: Python 3.
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Aps Filesystem Agent is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 4k tokens (SKILL.md is roughly 16k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 3.1k tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Aps Filesystem Agent: Capture Conversation (outline/outline, 41k stars), Project Cairn (iBlinkQ/project-cairn, 235 stars), LLM Wiki Knowledge Graph (Egonex-AI/Understand-Anything, 86k stars) and Find And Cite (outline/outline, 41k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
LeoYeAI (a GitHub user) maintains it in LeoYeAI/openclaw-master-skills, which has 2,159 GitHub stars. The repository holds 972 skills in this directory. The repository was last updated on July 20, 2026.
Source: LeoYeAI/openclaw-master-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.