playbooks

home / skills / arustydev / ai / template-new-skill

template-new-skill skill

/legacy/skills/template-new-skill

This skill generates a ready-to-use skeleton template for a new Claude Code Skill, including read-only file access, search utilities, and file discovery.

npx playbooks add skill arustydev/ai --skill template-new-skill

Review the files below or copy the command above to add this skill to your agents.

Files (12)
SKILL.md
564 B
---
name: template-new-skill
description: Generate a skeleton template for a new Claude Code Skill.
allowed-tools: Read, Grep, Glob, Bash:just
id: B90F6D72-BB47-434C-8BDC-3C880E13AC9A
---

# Template New Skill

This Skill provides read-only file access.

## Instructions

1. Use Read to view file contents
2. Use Grep to search within files
3. Use Glob to find files by pattern

## Requirements

Packages must be installed in your environment:

```bash
NAME="skill name here" \
SCOPE="personal||project" \
DESC="Some description of the skill here" \
just init
```

Overview

This skill generates a minimal skeleton template for a new Claude Code Skill focused on Jupyter Notebook projects. It provides the basic file layout, simple instructions, and a small set of commands to bootstrap a personal or project-scoped skill. The template is read-only and intended as a starting point for developers to customize.

How this skill works

The skill inspects repository files using read-only operations: it can open files to show contents, grep to search inside files, and glob to list files by pattern. It returns a concise skeleton including a name, scope, description placeholders, and a basic initialization command to run in a shell. The output is intended to be copied into a new project and edited to match the developer’s needs.

When to use it

  • Starting a new Claude Code Skill based on a Jupyter Notebook workflow
  • Creating a lightweight, documented template for others to follow
  • Bootstrapping a personal or project-scoped skill quickly
  • Standardizing skill structure across multiple projects
  • Sharing a reproducible example for onboarding or documentation

Best practices

  • Edit the NAME, SCOPE, and DESC placeholders to reflect the real purpose and visibility of the skill
  • Keep the template minimal: include only essential files and clear instructions
  • Verify required packages and environment steps before publishing the skill
  • Use descriptive commit messages when customizing the template for tracking changes
  • Run the provided init command in a controlled environment to avoid accidental global installs

Example use cases

  • Generate a notebook-centric skill skeleton for data analysis helpers
  • Provide a standardized starting point for internal developer tools in a project repo
  • Create a sharable example demonstrating how to expose read-only file access in a skill
  • Quickly scaffold a skill for prototyping new interactions with Jupyter content