Github Repository Settings

Organization

vanillagreencom

github-repository-settings

Load to preview, render or check a repository's selected review instruction files and local review pointer.

Overview

Publisher	vanillagreencom
Repository	`kendex`
Skill name	`github-repository-settings`
Stars	91
Forks	37
Bundled files	2
License	MIT
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.
2 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by vanillagreencom on GitHub. Read the source before you install it.

Installation

Install the Github Repository Settings 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/vanillagreencom/kendex/tree/main/.agents/skills/github-repository-settings
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/vanillagreencom/kendex/tree/main/.agents/skills/github-repository-settings

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

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/vanillagreencom/kendex.git /tmp/kendex
mkdir -p .claude/skills
cp -r /tmp/kendex/.agents/skills/github-repository-settings .claude/skills/github-repository-settings

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

Use it in TypingMind

Enable Github Repository Settings 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 Github Repository Settings 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 Github Repository Settings 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.

Project Instructions

Problems with a kendex-owned skill go through kendex report; check ownership in the file first.

GitHub repository settings

bash
.agents/skills/github-repository-settings/scripts/github-repository-settings adopt --dry-run
.agents/skills/github-repository-settings/scripts/github-repository-settings render
.agents/skills/github-repository-settings/scripts/github-repository-settings check
.agents/skills/github-repository-settings/scripts/github-repository-settings check --staged

Use adopt --dry-run to preview takeover without writes. Keep the existing bot-instructions manifest. The library reports hand edits and refuses symlinked preview targets. render writes the selected outputs. check compares them without writes. check --staged reads tracked settings and review files from the index. Process and private-file settings keep their working values and normal precedence. A nested settings file keeps its working values only when it is absent from HEAD and the index. A staged deletion stays absent even if its working file remains. Exit codes: 0 clean, 1 findings, 2 could not complete. Options and the check report contract: scripts/github-repository-settings --help.

Preview grants no write ownership. Use the existing bot-instructions adoption operation to take unmanaged content over before rendering it.

Before adoption, choose hosted or local for GITHUB_STANDARD_CHECK_LOCATION in the settings [env] table. It has no default. When both adoption keys are empty or absent, check reports not adopted and exits 0 without judging review files. This package reports the value during check; it installs no hosted CI. GITHUB_STANDARD_BOT_REVIEW defaults to off. Off selects the library's local output. On selects its full output and the bots enabled in the manifest. Local output requires the manifest's codex flag and an installed bot-instructions package inside the checkout. The settings example declares the settings.

bot-instructions is the temporary renderer, schema and validator dependency. KEN-2362 removes that dependency after the ownership transition. review-gate provides the existing settings reader. Install these required packages beside this package. The catalog must pass its dependency and render checks with the latest released kendex engine. Release any required engine support before adopting catalog content that needs it.

This package declares no repository effects. Installation does not transfer the existing bot-instructions effects. For staged review-file checker selection, follow commit-guards/SKILL.md § Git hooks.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Github Repository Settings AI skill do?

Load to preview, render or check a repository's selected review instruction files and local review pointer.

Why use Github Repository Settings on TypingMind?

Because you install it once and use it with any model. Github Repository Settings 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 Github Repository Settings in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/vanillagreencom/kendex/tree/main/.agents/skills/github-repository-settings. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Github Repository Settings?

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 Github Repository Settings?

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

Is the Github Repository Settings AI skill free?

Yes. It is published on GitHub by vanillagreencom under the MIT license. 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

Discord Clawd

openclaw

OrganizationPopular

Use to talk to the Discord-backed OpenClaw agent/session; not for archive search.

Discrawl

Discord archive: search, sync freshness, DMs, summaries, TUI, repo/release work.

Gitcrawl

GitHub archive: issue/PR search, sync freshness, duplicate clusters, current GitHub handoff, and Gitcrawl repo work.

Graincrawl

Granola archive: search, sync freshness, notes, transcripts, panels, SQL counts, and Graincrawl repo work.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Project Instructions

GitHub repository settings

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now