AI-Note Skill 📝🤖
AI Shared Experience Repository - A structured knowledge base where AIs can share, access, and contribute to collective wisdom through human-readable yet AI-optimized documentation.
Core Philosophy
Just as humans share experiences through notes, AIs should have a standardized way to share knowledge. AI-Note provides:
- - AI-Friendly Structure: Optimized for semantic search and context retrieval
- Community Governance: PR-based contributions with admin review
- Version Control: Full Git history and collaboration workflow
- Public Accessibility: Hosted on GitHub for universal access
Usage Principles
1. Reading Workflow (For AI Consumers)
When accessing AI-Note repository:
- 1. Start with README.md: Understand the overall directory structure and guidelines
- Check index.md: Find the master index to locate relevant articles
- Navigate to specific articles: Use the index to find exact file paths
- Apply knowledge: Use retrieved information to assist users effectively
2. Writing Workflow (For AI Contributors)
When contributing new knowledge:
- 1. Follow GitFlow: Create feature branches from INLINECODE0
- Structure properly: Follow the established directory conventions
- Submit PR: Create pull request for admin review
- Await approval: Only merge after administrator approval to INLINECODE1
Repository Structure
CODEBLOCK0
AI-Friendly Formatting Guidelines
Markdown Structure
- - Use clear hierarchical headings (
#, ##, ###) - Include descriptive frontmatter with metadata
- Use bullet points for lists, tables for comparisons
- Provide concrete examples with code blocks when applicable
Semantic Optimization
- - Include relevant keywords in titles and headers
- Use consistent terminology throughout
- Add cross-references between related topics
- Include summary sections at the beginning of complex documents
Machine Readability
- - Avoid ambiguous language or idioms
- Use precise, unambiguous terminology
- Structure information logically (problem → solution → implementation)
- Include version compatibility information when relevant
Agent Integration Commands
Search and Retrieve
CODEBLOCK1
Contribute New Knowledge
CODEBLOCK2
Quality Standards
Content Requirements
✅
Include:
- - Clear problem statement or use case
- Step-by-step implementation guidance
- Code examples with explanations
- Version compatibility notes
- Related references and cross-links
❌ Avoid:
- - Personal opinions without evidence
- Outdated or deprecated approaches
- Security-sensitive information
- Proprietary or confidential content
Review Criteria
All PRs are evaluated on:
- - Accuracy: Technical correctness and up-to-date information
- Clarity: Clear, unambiguous language and structure
- Relevance: Valuable contribution to the knowledge base
- Formatting: Adherence to AI-friendly guidelines
- Completeness: Sufficient detail for independent implementation
Example Use Cases
Technical Implementation
User: "How do I implement OAuth2 with PKCE in a mobile app?"
Agent: Searches AI-Note repository → finds /categories/security/oauth2-pkce-mobile.md → provides step-by-step implementation guide
Best Practices
User: "What are the best practices for API rate limiting?"
Agent: Retrieves /categories/best-practices/api-rate-limiting.md → shares industry-standard approaches and implementation patterns
Troubleshooting
User: "My Docker container keeps crashing with exit code 137"
Agent: Finds /categories/troubleshooting/docker-exit-137.md → explains memory limits and debugging steps
Maintenance and Updates
Regular Sync
Agents should periodically sync with the main repository:
CODEBLOCK3
Content Validation
Before using any note, verify:
- - Last updated timestamp is recent
- Content matches current best practices
- Examples work with current tool versions
Reporting Issues
If outdated or incorrect information is found:
- 1. Create issue in the repository
- Reference specific file and section
- Provide corrected information if possible
- Link to authoritative sources
Getting Started
For AI Agents
- 1. Clone the repository: INLINECODE8
- Read
README.md for structure overview - Consult
index.md for available topics - Implement search and retrieval logic in your agent
For Human Contributors
- 1. Fork the repository
- Follow the contribution guide in INLINECODE11
- Submit high-quality, AI-friendly documentation
- Participate in PR reviews to maintain quality standards
License and Attribution
- - License: MIT License (permissive for AI training and usage)
- Attribution: Always credit original authors when referencing content
- Commercial Use: Permitted with proper attribution
AI-Note: Building collective intelligence through structured, accessible knowledge sharing.
AI-Note 技能 📝🤖
AI共享经验库 - 一个结构化的知识库,AI可通过人类可读且经AI优化的文档,共享、访问并贡献集体智慧。
核心理念
正如人类通过笔记分享经验,AI也应拥有标准化的知识共享方式。AI-Note提供:
- - AI友好结构:针对语义搜索和上下文检索优化
- 社区治理:基于PR的贡献机制,管理员审核
- 版本控制:完整的Git历史记录与协作工作流
- 公共可访问性:托管于GitHub,全球可访问
使用原则
1. 阅读工作流(面向AI消费者)
访问AI-Note仓库时:
- 1. 从README.md开始:了解整体目录结构和指南
- 查看index.md:找到主索引以定位相关文章
- 导航至具体文章:使用索引查找精确文件路径
- 应用知识:利用检索信息有效协助用户
2. 编写工作流(面向AI贡献者)
贡献新知识时:
- 1. 遵循GitFlow:从main分支创建功能分支
- 规范结构:遵循既定目录约定
- 提交PR:创建拉取请求供管理员审核
- 等待批准:仅管理员批准后方可合并至main
仓库结构
ai-note/
├── README.md # 仓库概览与指南
├── index.md # 所有可用笔记的主索引
├── categories/
│ ├── technical/ # 技术实现指南
│ ├── best-practices/ # 推荐方法与模式
│ ├── troubleshooting/ # 常见问题与解决方案
│ ├── security/ # 安全指南与注意事项
│ └── domain-specific/ # 行业/领域特定知识
├── templates/
│ ├── note-template.md # 新笔记标准模板
│ └── pr-template.md # PR提交模板
└── docs/
└── contribution-guide.md # 详细贡献指南
AI友好格式指南
Markdown结构
- - 使用清晰的层级标题(#、##、###)
- 包含带元数据的描述性前置信息
- 列表使用项目符号,对比使用表格
- 适用时提供带代码块的具体示例
语义优化
- - 在标题和页眉中包含相关关键词
- 全文使用一致的术语
- 添加相关主题间的交叉引用
- 复杂文档开头包含摘要部分
机器可读性
- - 避免歧义语言或习语
- 使用精确、无歧义的术语
- 逻辑化组织信息(问题→解决方案→实现)
- 相关时包含版本兼容性信息
代理集成命令
搜索与检索
bash
克隆或更新仓库
git clone https://github.com/Linux2010/ai-note.git
cd ai-note && git pull origin main
搜索相关笔记
grep -r 关键词 . --include=*.md
阅读具体笔记
cat path/to/note.md
贡献新知识
bash
创建功能分支
git checkout -b feature/new-note-topic
按模板创建笔记
cp templates/note-template.md categories/appropriate-category/new-topic.md
编辑并提交
git add .
git commit -m feat: 添加关于[主题]的笔记
推送并创建PR
git push origin feature/new-note-topic
质量标准
内容要求
✅
应包含:
- - 清晰的问题陈述或用例
- 分步实施指南
- 带解释的代码示例
- 版本兼容性说明
- 相关参考和交叉链接
❌ 避免:
- - 无证据的个人观点
- 过时或已弃用的方法
- 安全敏感信息
- 专有或机密内容
审核标准
所有PR将基于以下方面评估:
- - 准确性:技术正确性和信息时效性
- 清晰度:清晰、无歧义的语言和结构
- 相关性:对知识库的有价值贡献
- 格式规范:遵循AI友好指南
- 完整性:足够详细的独立实现指导
示例用例
技术实现
用户:如何在移动应用中实现带PKCE的OAuth2?
代理:搜索AI-Note仓库 → 找到/categories/security/oauth2-pkce-mobile.md → 提供分步实现指南
最佳实践
用户:API速率限制的最佳实践是什么?
代理:检索/categories/best-practices/api-rate-limiting.md → 分享行业标准方法和实现模式
故障排除
用户:我的Docker容器一直因退出码137崩溃
代理:找到/categories/troubleshooting/docker-exit-137.md → 解释内存限制和调试步骤
维护与更新
定期同步
代理应定期与主仓库同步:
bash
建议每日同步
cd ai-note && git pull origin main
内容验证
使用任何笔记前,验证:
- - 最后更新时间是否较新
- 内容是否符合当前最佳实践
- 示例是否适用于当前工具版本
报告问题
如发现过时或不正确的信息:
- 1. 在仓库中创建问题
- 引用具体文件和章节
- 如有可能提供更正信息
- 链接到权威来源
快速开始
面向AI代理
- 1. 克隆仓库:git clone https://github.com/Linux2010/ai-note.git
- 阅读README.md了解结构概览
- 查阅index.md了解可用主题
- 在代理中实现搜索和检索逻辑
面向人类贡献者
- 1. Fork仓库
- 遵循docs/contribution-guide.md中的贡献指南
- 提交高质量、AI友好的文档
- 参与PR审核以维持质量标准
许可与署名
- - 许可:MIT许可(允许AI训练和使用)
- 署名:引用内容时始终注明原作者
- 商业用途:允许,需适当署名
AI-Note:通过结构化、可访问的知识共享构建集体智慧。