share-skill

To publish local skills to a Notion database, you can push validated local skill bundles to a centralized repository. This process handles metadata extraction, file packaging, and team assignment to enable cross-team discovery and centralized access to reusable workflow assets.

Duplicate detection for skill sharing blocks overwrites of existing skills in the centralized knowledge base. This mechanism maintains clear ownership, preserves version history, and ensures audit trails remain intact by preventing invalid or redundant entries during post-creation publishing workflows.

You can automatically categorize workflow automation skills by team during upload. The system infers the correct team assignment, such as General, Solutions, Engineering, or Sales, based on the skill's purpose, while requesting user confirmation to ensure accurate categorization in the database.

You need a valid SKILL.md format for skill bundles before uploading to a Notion knowledge management system. The system automatically checks the format to prevent invalid entries, ensuring your workflow assets meet the requirements for auditable skill sharing.

The best way to track versions of team collaboration skills is to push them to a centralized Notion database. This approach satisfies requirements for auditable skill sharing and version tracking by blocking overwrites, thereby maintaining clear ownership of reusable workflow assets.

You need to validate SKILL.md files before pushing them to a skills database to prevent invalid entries. Validated uploads check the format automatically, ensuring that only properly structured skill bundles are packaged and shared for cross-team discovery.