collections
/collections
Guidelines for creating and managing awesome-copilot collections Triggers on: collections/*.collection.yml
- Author
- pingqLIN ↗
- Repository
- skill-0 ↗
- Licence
- MIT
- Last repository change
- 18.07.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 18.07.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Guidelines for creating and managing awesome-copilot collections Triggers on: collections/*.collection.yml
Original author description
Guidelines for creating and managing awesome-copilot collections Triggers on: collections/*.collection.yml
How it works
- Collection Instructions
- Collection Structure
- Validation Rules
- Best Practices
- File Organization
- Generation Process
SKILL.md preview
--- name: collections description: Guidelines for creating and managing awesome-copilot collections Triggers on: collections/*.collection.yml triggers: "collections/*.collection.yml" globs: "collections/*.collection.yml" --- # Collections Development ## Collection Instructions When working with collections in the awesome-copilot repository: - Always validate collections using `node validate-collections.js` before committing - Follow the established YAML schema for collection manifests - Reference only existing files in the repository - Use descriptive collection IDs with lowercase letters, numbers, and hyphens - Keep collections focused on specific workflows or themes - Test that all referenced items work well together ## Collection Structure - **Required fields**: id, name, description, items - **Optional fields**: tags, display - **Item requirements**: path must exist, kind must match file extension - **Display options**: ordering (alpha/manual), show_badge (true/false) ## Validation Rules - Collection IDs must be unique across all collections - File paths must exist and match the item kind - Tags must use lowercase letters, numbers, and hyphens only - Collections must contain 1-50 items - Descriptions must be 1-500 characters ## Best Practices - Group 3-10 related items for optimal usability - Use clear, descriptive names and descriptions - Add relevant tags for discoverability - Test the complete workflow the collection enables - Ensure items complement each other effectively ## File Organization - Collections don't require file reorganization - Items can be located anywhere in the repository - Use relative paths from repository root - Maintain existing directory structure (prompts/, instructions/, agents/) ## Generation Process - Collections automatically generate README files via `npm start` - Individual collection pages are created in collections/ directory - Main collections overview is generated as README.collections.md - VS Code install badges are automatically created for each item
Versions
The database has no other skills named collections.
Database snapshot: 13.11.2026 · package version c67273682cf7 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100collections-development
Design JSON Schema collections and CRUD patterns for Falcon Foundry apps. TRIGGER when user asks to "create a collection", "define a JSON schema", "store data in Foundry", runs `foundry collections create`, or needs help with indexable fields, FQL queries, or collection access… - 100pb-collections
Collection and schema design for PocketBase. Use when creating collections, designing schemas, adding fields, setting up relations, or choosing between base/auth/view collection types. Prevents wrong field types, documents zero-default behavior, and covers relation cascading. - 100arc-collection
Qdrant collection management for semantic search. Use when user mentions managing collections, creating collection, listing collections, verifying collection integrity, exporting or importing collections, or viewing indexed items in Qdrant. - 100awesome-dsh-submit
把 DSH 插件仓库提交到 awesome-dsh-plugin 列表(在 data/plugins 下新增一个 owner__repo.yml 条目并开 PR)。当用户说"把这个插件提交到 awesome 列表""给某个 dsh 插件提 awesome PR""这个 PR 的 CI 结果怎样/有没有被合并"时使用。流程是:先体检仓库是否满足上游硬性条件(dsh.bundle 清单、补丁文件、dsh-plugin topic、创建满 24 小时、尚未收录),再写条目文件,再用 gh api 建分支并开 PR,最后读 CI 与合并状态。不用于提交到… - 85Scala Collections
Use when scala collections including immutable/mutable variants, List, Vector, Set, Map operations, collection transformations, lazy evaluation with views, parallel collections, and custom collection builders for efficient data processing. - 90java-collections
Select Java collections by access pattern, use streams where they clarify, and default to immutability and records. Use when modeling data in Java or reviewing collection-heavy code.