mirror of
https://github.com/InsForge/insforge-skills.git
synced 2026-09-14 16:03:59 +08:00
908a6c05c6
Prep for submission to the Claude community plugin directory: - License: LICENSE is Apache 2.0 but all manifests declared MIT. Align every declaration to Apache-2.0 (plugin.json, marketplace.json, the four SKILL.md frontmatters, README, CONTRIBUTING, AGENTS). - README integrations summary: add Better Auth and OKX x402 (both shipped but previously undocumented). - README structure tree: rewrite insforge-cli / insforge-debug / insforge-integrations subtrees to match the real flat references/*.md layout instead of the stale per-provider SKILL.md dirs. - marketplace.json metadata version 1.0.0 -> 1.2.0 to match the plugin. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2.6 KiB
2.6 KiB
Contributing to InsForge Agent Skills
Thank you for your interest in contributing to InsForge Agent Skills! This document provides guidelines for contributing to this repository.
Getting Started
- Fork this repository
- Clone your fork locally
- Create a branch for your changes
Skill Format
This repository follows the Agent Skills Open Standard. Please review the specification before contributing.
SKILL.md Requirements
Every skill must have a SKILL.md file with:
---
name: skill-name # Required: lowercase, hyphens only, matches directory name
description: | # Required: clear description of what the skill does
Description here...
license: Apache-2.0 # Optional: license identifier
metadata: # Optional: additional metadata
author: insforge
version: "1.0.0"
---
# Skill content in Markdown...
Documentation Files
For InsForge modules, keep documentation focused on the app or platform surface being used:
sdk-integration.md: Client-side SDK usage with@insforge/sdk- Specialized guides: Backend, security, protocol, or workflow-specific references such as RLS, pgvector, S3-compatible storage, or capability guides
Documentation Guidelines
Structure
Each documentation file should include:
- Title and Overview: Brief description of the module
- Setup/Prerequisites: Required configuration or imports
- Usage Examples: Practical code examples
- Best Practices: Recommended patterns
- Common Mistakes: What to avoid with solutions
Code Examples
- Keep examples concise and runnable
- Use consistent formatting
- Include both correct and incorrect examples where helpful
- Show the
{ data, error }return pattern
// Good: Shows complete pattern
const { data, error } = await insforge.database.from('posts').select()
if (error) {
console.error(error)
return
}
console.log(data)
Writing Style
- Use clear, direct language
- Prefer active voice
- Keep explanations brief
- Use tables for reference information
Adding a New Module
- Create a directory under
skills/insforge/ - Add the required documentation files
- Update the module reference table in
skills/insforge/SKILL.md - Test that all links work correctly
Pull Request Process
- Ensure your changes follow the format guidelines
- Update relevant documentation if adding features
- Submit a pull request with a clear description
- Respond to any feedback from reviewers
Questions?
If you have questions about contributing, please open an issue for discussion.