IM 知识整理和分析技能,专注于从聊天记录中提取高价值的知识
npx skills add https://github.com/cafe3310/public-agent-skills --skill im-local-kb
01 目录下的实际文本证据。01-chats-input-organized 中已归档的历史数据。所有修正必须通过追加内容实现。[来源: 产品群/2023-10.md])。tasks/ 目录下的任务状态文件,记录当前处理进度,避免重复劳动或遗漏。kb/
├── 00-chats-input-raw/ # [输入层] 原始堆积区
│ └── {raw_input_name}.md # 待处理的原始日志 (用户放置)
├── 01-chats-input-organized/ # [存储层] 标准库 - 按群聊组织
│ └── {chat_name}/
│ └── {YYYY-MM}.md # 标准化的月度日志
├── 10-chats-input-raw-used/ # [归档层] 已消费的原始日志 (结构化归档)
│ └── {raw_input_name}.md
├── 02-project-specs/ # [配置层] 项目定义
│ ├── proj_{project_id}.yaml # 定义提取范围与目标
│ └── notes.yaml # 各群聊/单聊的零散备注记录
├── 03-missing-periods/ # [诊断层] 缺失报告
│ └── gap_{project_id}.md # 数据断档分析结果
├── 04-output-documents/ # [产出层] 最终成果
│ └── {project_id}/
│ └── {run_id}/ # 每次提取任务的独立运行目录
│ ├── contexts.md # 该任务的全量上下文
│ ├── added-contexts.md # (仅增量模式) 新增的上下文
│ ├── output-{idx}.md # 物理合并后的最终报告
│ └── output-{idx}-chunk-{no}.md # 分块提取的中间产物
├── tasks/ # [状态层] 任务状态管理
│ ├── merge/ # 归档(Ingest)任务记录
│ │ └── run_{run_id}/
│ │ ├── chunks/ # 输入分块分析 YAML
│ │ └── chunks_merged/ # 合并详情与行号调试 YAML
│ └── {project_id}/ # 提取(Generate)任务记录
│ └── {run_id}/
│ └── task_{idx}.yaml # 每个目标的进度状态 (Pending/Done)
└── backups/ # [备份层] 全量备份存储区
└── backup_{timestamp}.zip
根据用户意图,选择以下流程之一执行:
workflows/01_ingest/WORKFLOW_ingest.mdworkflows/02_gap_check/WORKFLOW_gap_check.mdworkflows/03_generate/WORKFLOW_generate.mdworkflows/util_notes/WORKFLOW_notes.md本 Skill 的工程目录按功能模块化分布,以便于维护和快速调用:
.gemini/skills/im-local-kb/
├── SKILL.md # 核心定义与路由概览
├── USER_GUIDE.md # 面向用户的操作指南
├── agents/ # 这个 Skill 所需的 Sub-Agent。你需要用合理方法安装到你的主 Agent。
├── template_kb/ # [范例] 真实的知识库结构模板
├── workflows/ # [执行层] 按功能阶段划分的逻辑
│ ├── 01_ingest/ # 数据清洗与归档模块
│ ├── 02_gap_check/ # 完整性校验模块
│ ├── 03_generate/ # 知识提取与报告生成模块
│ ├── util_backup/ # 实用工具:备份
│ ├── util_notes/ # 实用工具:备注管理
│ └── util_validate/ # 实用工具:校验
└── tobewritten.md # 待整理的技术细节与进阶文档
Integration with protocols.io API for managing scientific protocols. This skill should be used when working with protocols.io to search, create, update, or publish protocols; manage protocol steps and materials; handle discussions and comments; organize workspaces; upload and manage files; or integrate protocols.io functionality into workflows. Applicable for protocol discovery, collaborative protocol development, experiment tracking, lab protocol management, and scientific documentation.
Analyzes job descriptions and generates tailored resumes that highlight relevant experience, skills, and achievements to maximize interview chances
Generate Excalidraw diagrams from natural language descriptions. Use when asked to "create a diagram", "make a flowchart", "visualize a process", "draw a system architecture", "create a mind map", or "generate an Excalidraw file". Supports flowcharts, relationship diagrams, mind maps, and system architecture diagrams. Outputs .excalidraw JSON files that can be opened directly in Excalidraw.
Build and distribute Expo development clients locally or via TestFlight
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Data structure for annotated matrices in single-cell analysis. Use when working with .h5ad files or integrating with the scverse ecosystem. This is the data format skill—for analysis workflows use scanpy; for probabilistic models use scvi-tools; for population-scale queries use cellxgene-census.
Benchling R&D platform integration. Access registry (DNA, proteins), inventory, ELN entries, workflows via API, build Benchling Apps, query Data Warehouse, for lab data management automation.
Comprehensive molecular biology toolkit. Use for sequence manipulation, file parsing (FASTA/GenBank/PDB), phylogenetics, and programmatic NCBI/PubMed access (Bio.Entrez). Best for batch processing, custom bioinformatics pipelines, BLAST automation. For quick lookups use gget; for multi-service integration use bioservices.
Take cafe3310/im-local-kb from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.