explaingit

oscabriel/skills

Analysis updated 2026-05-18

51Audience · developerComplexity · 2/5Setup · easy

TLDR

A small pack of AI coding assistant skills: one that researches libraries by cloning and reading their real source, and one that turns approved design docs into typed code scaffolding.

Mindmap

A visual breakdown will appear here once this repo is fully enriched.

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

What do people build with it?

USE CASE 1

Ask your AI assistant to research an external library by cloning it locally and reading the actual source code.

USE CASE 2

Get answers about open-source project internals backed by a specific commit, file, and line range.

USE CASE 3

Turn an approved architecture or domain document into typed domain models and service boundaries before writing feature code.

What is it built with?

skills.sh

How does it compare?

oscabriel/skills709166872-cpu/tagcast-aiadvdebug/brovan
Stars515151
LanguageHTMLC#
Setup difficultyeasymoderatemoderate
Complexity2/54/55/5
Audiencedeveloperdatadeveloper

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · easy Time to first run · 5min

Requires an AI coding assistant that supports skills, installed via the skills.sh CLI.

The README does not state a license.

In plain English

This repository contains a small collection of agent skills, which are instruction files that AI coding assistants can follow as slash commands. The repository is designed to be installed as a unit via a tool called skills.sh, which makes all included skills available to your AI assistant in one step. The first skill is called Replicant. It instructs an AI agent to research external code repositories by cloning them locally rather than relying on web search, cached documentation, or generated summaries. When you ask about a library, framework, or open-source project, Replicant tells the agent to check a local folder of clones first, clone the repository if it is missing, and then read the actual source files to answer your question. Configuration options include where to store clones, whether to update existing ones automatically, and whether to use full or shallow history. Answers from Replicant include the specific commit, file path, and line range the information came from. The second skill is called Docs to Types. It is meant for the moment after a project has produced design decisions, domain definitions, or architecture records, but before any feature code is written. The skill instructs an agent to turn that approved context into typed code structure: domain types, error types, service boundaries, state models, smart constructors, and module layout. It is not intended to produce business logic or full implementations. The readme recommends running a separate grilling session first to produce the input context documents. Both skills are aimed at developers who work closely with AI coding assistants and want structured, repeatable behavior for specific research and architecture tasks. The repository itself contains no application code.

Copy-paste prompts

Prompt 1
Install oscabriel/skills with skills.sh and explain what the Replicant and Docs to Types skills each do.
Prompt 2
Use replicant to look up how a specific open-source library implements a feature, citing the exact file and commit.
Prompt 3
Set up the Replicant clone shelf with a chosen clone root, update policy, and clone depth.
Prompt 4
Use docs-to-types to turn my approved architecture notes into domain types and typed error boundaries.

Frequently asked questions

What is skills?

A small pack of AI coding assistant skills: one that researches libraries by cloning and reading their real source, and one that turns approved design docs into typed code scaffolding.

What license does skills use?

The README does not state a license.

How hard is skills to set up?

Setup difficulty is rated easy, with roughly 5min to a first successful run.

Who is skills for?

Mainly developer.

Open on GitHub → Explain another repo

This repo across BitVibe Labs

Verify against the repo before relying on details.