Open Source Prep

Community

krishnakanthb13

open_source_prep

Comprehensive workflow to prepare a project for public open-source release. Handles licensing, username normalization, code integrity checks, and documentation generation.

Overview

Publisher	krishnakanthb13
Repository	`antigravity_global_skills`
Skill name	`open_source_prep`
Stars	66
Forks	11
Bundled files	Instructions only
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by krishnakanthb13 on GitHub. Read the source before you install it.

Installation

Install the Open Source Prep AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/krishnakanthb13/antigravity_global_skills/tree/main/open_source_prep
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/krishnakanthb13/antigravity_global_skills.git /tmp/antigravity_global_skills
mkdir -p .claude/skills
cp -r /tmp/antigravity_global_skills/open_source_prep .claude/skills/open_source_prep

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Open Source Prep in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Open Source Prep on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Open Source Prep is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Open Source Release Preparation

This skill guides you through the process of preparing a project for a public GitHub release.

Inputs

GitHub Username: The target username for links/licensing.
Project Root: The directory to prep.

Tooling Strategy

Use grep_search to find placeholders (YOUR_USERNAME).
Use replace_file_content to update files.
Use run_command (curl) to fetch licenses.

0. Code Integrity & Feature Verification

Before touching documentation:

Verification: Ensure all major parts of the codebase work together. identify broken flows or unused modules.
Clarification: Explain all features and their interactions.
Assumptions: explicitly call out limitations or expected runtime behaviors.

1. License Management

Check for LICENSE file:
- If exists: Add the standard header:
  - Project Name & one-line description
  - Copyright (C) 2026 Krishna Kanth B
  - Standard GPL v3 boilerplate notice.
  - Separator line.
- If missing: Download GPL v3 text (use curl https://www.gnu.org/licenses/gpl-3.0.txt) and prepend the header above.

2. Username Standardization

Search and replace the following placeholders with krishnakanthb13:

YOUR_USERNAME
your-username
YOUR-USERNAME
<username>

Scope: README.md, CONTRIBUTING.md, config files, scripts, and comments.

3. Documentation Suite

A. CODE_DOCUMENTATION.md

Source inspiration: codewalkthrough.md or code_readme.md (if they exist).
Structure:
1. File & Folder structure with descriptions.
2. High-level architecture.
3. Core modules/functions table.
4. Data flow (ASCII/Mermaid diagrams).
5. Dependencies (runtime vs dev).
6. Execution flow (Entry -> Output).

B. DESIGN_PHILOSOPHY.md

Source inspiration: walkthrough.md or context_readme.md (if they exist).
Content:
1. Problem definition.
2. Why this solution?
3. Design Principles (Simplicity, Performance, etc.).
4. Target Audience & Use Cases.
5. Real-world workflow fit.
6. Trade-offs & Constraints.

C. CONTRIBUTING.md

Create if missing.
Content:
1. Bug reporting formats.
2. Feature suggestion process.
3. Workflow: Fork -> Branch -> PR.
4. Local dev setup.
5. Pre-submission checklist (Testing/Validation).

D. SECURITY.md & CODE_OF_CONDUCT.md

SECURITY.md: Provide clear instructions on how to report vulnerabilities privately (e.g., security email) and supported versions.
CODE_OF_CONDUCT.md: Adopt a standard code of conduct (e.g., Contributor Covenant) to establish community guidelines.

E. Issue & PR Templates

Create .github/ISSUE_TEMPLATE/ folder.
Add bug_report.md (Steps to reproduce, Expected vs Actual, Environment).
Add feature_request.md (Problem, Proposed Solution, Alternatives).
Create .github/pull_request_template.md (Checklist for tests, docs, breaking changes).

4. Final Polish

Gitignore: Ensure secrets, logs, and artifacts are ignored.
References: Verify all file paths in docs are accurate.
Badges: Add GPL v3 badge to README.md.
Consistency: Ensure consistent naming and tone across all files.

Metadata

GitHub Username: krishnakanthb13
Copyright Holder: Krishna Kanth B

Frequently asked questions

What does the Open Source Prep AI skill do?

Comprehensive workflow to prepare a project for public open-source release. Handles licensing, username normalization, code integrity checks, and documentation generation.

Why use Open Source Prep on TypingMind?

Because you install it once and use it with any model. Open Source Prep is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Open Source Prep in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/krishnakanthb13/antigravity_global_skills/tree/main/open_source_prep. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Open Source Prep?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Open Source Prep?

As many as you like. As long as a model supports skills, you can use Open Source Prep with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Open Source Prep AI skill free?

It is published on GitHub by krishnakanthb13. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Mcp Dependency Review

affaan-m

CommunityPopular

Statically review MCP configuration for mutable package references before approval or CI, without executing discovered MCP servers. Use when reviewing .mcp.json, Cursor, VS Code, Claude, Windsurf, or…

Skill Host Compat

Lint ECC skills for Codex/Cursor-safe frontmatter and Claude-only substitutions before a skill PR.

Brand Discovery

Use when a brand needs to discover or articulate its identity through structured multi-session interviews. Covers purpose, positioning, audience, personality, voice, narrative, and founder-brand…

Bun Runtime

Bun as runtime, package manager, bundler, and test runner. When to choose Bun vs Node, migration notes, and Vercel support.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Open Source Release Preparation

Inputs

Tooling Strategy

0. Code Integrity & Feature Verification

1. License Management

2. Username Standardization

3. Documentation Suite

A. CODE_DOCUMENTATION.md

B. DESIGN_PHILOSOPHY.md

C. CONTRIBUTING.md

D. SECURITY.md & CODE_OF_CONDUCT.md

E. Issue & PR Templates

4. Final Polish

Metadata

Frequently asked questions

Related AI Skills

Set up your own AI workspace now