$ show shareAI-lab/lab-skills
This is a knowledge/content repository, not a running software system: a curated collection of 11 'Agent Skills' packages compliant with the Agent Skills specification (agentskills.io), designed to be loaded on-demand by AI coding agents (Claude Code, Codex, Cursor, etc.) and other LLM runtimes. Each package is a self-contained directory with a SKILL.md entry point (YAML frontmatter with name/description plus routing instructions), plus references/, assets/, scripts/, and optional agents/ metadata. The skills cover research-analysis (deep-architecture-research with a confirmation-gate and evidence-ledger protocol; neural-mechanism-research; review-ai-conversations with reverse-engineered adapters for Claude Code, Codex, opencode, Grok Build, and Cursor conversation stores; understanding-first-report), software engineering (vibe-coding with scenario/domain/phases sub-references), team collaboration (meeting-coach-leader/worker), agent development (agent-builder with actual Python starter code; skill-judge with a 120-point rubric), and content publishing (media-writer for 7 platforms). There is no application entry point, server, or pipeline; the 'product' is the instructional content and routing logic itself. Although classified as application due to its standalone Python tools and operational guidance (rather than data pipeline), the repo is fundamentally a hybrid: most value comes from the rigor of its written protocols and evaluation rubrics, not executable code. The only real code lives in agent-builder (~4 self-contained Python files: minimal-agent.py, subagent-pattern.py, tool-templates.py, init_agent.py) which implement a clean, security-conscious agent loop. The most impressive craft is the data-engineering-style documentation in review-ai-conversations, which precisely specifies the storage schemas (SQLite tables, JSONL shapes, lineage/parent-child rules) of five proprietary agent tools, each fact tagged with provenance evidence ([CODE]/[DOC]/[ISSUE]) and version-pinned research dates. The skill-judge rubric and deep-architecture evidence protocol likewise demonstrate non-trivial expertise: hard gates, severity levels, evidence-vs-inference discipline, and explicit anti-patterns. The repo is actively maintained (last commit 2026-09-16, in-repo evidence research dated 2026-08-23, plus a documented skill-rename migration path in the READMEs, which exist in English, Chinese, and Japanese). Technical drift is low: the pinned model (claude-sonnet-4-20250514), SDK usage, and cited external tools (Codex 0.148.0, Cursor 2026.08) are current. No test suite exists, but that is the wrong bar for a documentation-oriented collection; the applicable standards are structural validity, evidence quality, and progressive-disclosure design, which are handled well. Weaknesses: media-writer's platform guides are somewhat generic social-media advice, some philosophical prose is repetitive, and the Python examples lack a requirements.txt/pinned dependency file.
The LLM identified 6 files worth highlighting for reuse:
An ~80-line, self-contained minimal working agent template implementing the loop 'model decides act-or-respond -> execute tool -> continue'. Demonstrates non-obvious craft: safe_path() prevents path-traversal outside the workspace, bash execution requires interactive user approval unless AGENT_ALLOW_SHELL=1, and tool outputs are truncated/isolated. Clarifies that this is a learning-oriented reference, not a security boundary. Could be extracted into any new agent project with Anthropic SDK with minimal modification.
Implements the Task tool pattern with isolated child-agent context to prevent parent context pollution. Key design: an AGENT_TYPES registry with role-scoped tool whitelists (explore=read-only, code=all, plan=read-only), exclusive child tool filtering (subagents never get the Task tool, preventing infinite recursion), fresh message history per spawn, and return of only a concise summary to the parent. Includes in-place progress rendering. A clean, extractable pattern for any multi-agent orchestration system.
A copy-and-customize toolkit of agent tool definitions plus implementations: bash (with timeout, 50KB output cap, and interactive shell-approval gate), read_file (with line limits), write_file (auto-mkdir parents), edit_file (exact-match, single-occurrence replacement for safety). Includes safe_path() path-escape prevention and a clean dispatcher pattern that makes adding new tools a 3-step process. Demonstrates proportionate security handling (operational limits, not a fake sandbox boundary). Highly reusable across agent builders.
A CLI scaffold script that generates a complete, inspectable agent project (level 0: ~70-line single-bash agent; level 1: ~200-line 4-tool agent) with embedded templates, .env.example, and .gitignore. Shows non-obvious craft: strict name validation via regex, refusal to overwrite existing targets, safe output-dir resolution, and explicit security warnings about AGENT_ALLOW_SHELL in the generated project. A reusable, parameterized code-generation pattern applicable to any scaffolding tool.
A 120-point, 8-dimension rubric for evaluating the quality of AI skill packages (knowledge delta, thinking patterns, anti-pattern quality, trigger quality, progressive disclosure, freedom calibration, structural pattern fit, practical usability) with concrete score anchors per dimension and grade bands. Includes strong evidence discipline: every score must cite a file location and behavioral consequence, avoid false precision, and hard-gate failures override any score. A thoughtfully calibrated evaluation framework that applies far beyond this repo to any prompt-instruction or agent-skill package.
The standout data-engineering artifact: a version-pinned, evidence-tagged specification of the local storage formats (SQLite schemas, JSONL shapes, fork/child-parent/compaction/rewind lineage rules) for Claude Code, Codex CLI/Desktop, opencode, Grok Build, and Cursor IDE/CLI conversation stores. Every adapter finding is tagged [CODE]/[DOC]/[HIST]/[ISSUE]/[OBSERVED] with specific commit hashes, release versions, and maintainer-issue links, and records both what was verified locally and what is unverifiable. Establishes canonical-vs-derived distinction (e.g., Codex state_5.sqlite outranks history.jsonl; Cursor conversation-search.db is a candidate cache, not body truth) — genuine, reusable reverse-engineering documentation pattern for on-disk data recovery.