Describe Repository

VerifiedCaution

Updates Git repository metadata (description, tags) by analyzing repository context and user-provided information. Helps keep repository descriptions and categorization consistent across work and personal projects.

Sby Skills Guide Bot
DocumentationIntermediate
6/2/2026
Claude Code
#repository-metadata#repo-description#git-management#project-onboarding

Recommended for

Automated summary

This skill adds or updates repository metadata (description, tags, team) using an integrated Python script.

Strengths

  • Automates repository metadata updates from a natural language description.
  • Detects machine and OS context for personalized information.
  • Stores metadata in a central configuration repository for future reference.

Limitations

  • Requires the YW_CONFIG_REPO_PATH environment variable to be set.
  • Depends on a Python script and an optional virtual environment.
  • Designed for a personal workflow, not directly reusable without adaptation.
When to use it

Use when documenting a repository (new or existing) with a structured description and tags.

When not to use it

Avoid if you don't need persistent metadata or if the environment is not configured.

Security analysis

Caution
Quality score88/100

The skill uses bash, pip, and arbitrary Python script execution, which introduces risk if the skill's script or dependencies are malicious. However, there is no indication of intentional harm or data exfiltration; the instructions are transparent and focused on legitimate metadata management.

Findings
  • •Runs Python script with user-supplied arguments (description, tags), which could be leveraged if the script is compromised.
  • •Creates Python virtual environment and installs packages via pip, potentially downloading and executing untrusted code from a requirements.txt within the plugin directory.
  • •Executes bash commands for environment detection and script invocation, though the operations are standard and not destructive.
How this analysis is made

Examples

Describe a solutions repository
Hey, this repo contains Dynamics solution packages. We need Core-Platform approval for PRs.
Update a personal project description
This repository is my personal blog built with Hugo. Tags: blog, hugo, static-site.

name: describe-repo description: Add or update repository metadata and description version: 1.0 parameters:

  • name: description type: string description: Description of the repository required: true
  • name: tags type: array description: Tags for categorizing the repository optional: true agent: memory-manager

Describe Repository

This skill adds or updates metadata for the current repository.

Instructions for Agent

1. Identify Repository

  • Detect current repository path: git rev-parse --show-toplevel
  • Extract repository name from path
  • Get remote URL: git remote get-url origin
  • Determine category (work/personal) based on remote URL:
    • Contains "dev.azure.com" or company domain → work
    • Contains "github.com/yoshiwatanabe" → personal

2. Collect Metadata

From user's description, extract:

  • Main description: What the repository contains/does
  • Team information: If mentioned
  • Approval process: If mentioned (e.g., "needs Core-Platform approval")
  • Special notes: Any important context
  • Tags: From user parameter or inferred from description

Get current machine and OS context:

  • Machine: hostname (lowercase)
  • OS: Windows/WSL/Linux

3. Call Python Script

Get configuration repository path:

  • Read YW_CONFIG_REPO_PATH environment variable (required)
  • If not set, return error: "Please set YW_CONFIG_REPO_PATH in ~/.claude/settings.json. See installation guide for WSL path requirements."

Execute the script from plugin directory:

cd "${CLAUDE_PLUGIN_ROOT}"

# Detect Python command (python3 on Linux, python on Windows)
PYTHON_CMD=$(command -v python3 || command -v python)

# Try to use venv if available, create if needed, skip if venv creation fails
if [ -d "venv" ]; then
  # Activate venv (cross-platform)
  if [ -f "venv/bin/activate" ]; then
    source venv/bin/activate
  elif [ -f "venv/Scripts/activate" ]; then
    source venv/Scripts/activate
  fi
elif $PYTHON_CMD -m venv venv 2>/dev/null; then
  echo "Setting up Python environment (first time)..."
  if [ -f "venv/bin/activate" ]; then
    source venv/bin/activate
  elif [ -f "venv/Scripts/activate" ]; then
    source venv/Scripts/activate
  fi
  pip install -r requirements.txt
else
  echo "Note: Using system Python (venv creation not available)"
fi

$PYTHON_CMD scripts/manage_memory.py describe-repo \
  --config-repo "$YW_CONFIG_REPO_PATH" \
  --repo-path {repo_path} \
  --description "{description}" \
  --tags "{tags}" \
  --machine {machine} \
  --os {os}

4. Handle Result

Parse the JSON output:

{
  "success": true,
  "repo_slug": "dynamics-solutions",
  "filepath": "memory/repositories/dynamics-solutions.md"
}

Return confirmation to the user:

Repository metadata updated!
- Repository: dynamics-solutions
- Description: [user's description]
- Tags: [tags if any]
- Synced to remote: Yes

Example Usage

User: "Hey, this repo contains Dynamics solution packages. We need Core-Platform approval for PRs."

Agent:

  1. Identifies current repository
  2. Extracts key information from description
  3. Calls manage_memory.py describe-repo
  4. Confirms metadata was saved

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/describe-repository-mm5t8ca9/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/describe-repository-mm5t8ca9' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/describe-repository-mm5t8ca9/download' --output '.skill-downloads/describe-repository-mm5t8ca9/SKILL.md.part' && mv '.skill-downloads/describe-repository-mm5t8ca9/SKILL.md.part' '.skill-downloads/describe-repository-mm5t8ca9/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/describe-repository-mm5t8ca9/SKILL.md' && test -s '.skill-downloads/describe-repository-mm5t8ca9/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/describe-repo' && cp -R '.skill-downloads/describe-repository-mm5t8ca9' '.claude/skills/describe-repo'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/describe-repository-mm5t8ca9'

openskills read 'describe-repository-mm5t8ca9'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/describe-repository-mm5t8ca9/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills