⏳ This skill is pending AI review.

Scores will appear once the review pipeline completes.

v1.0.0

Skill Name

smartrus@smartrus⭐ 0 stars· last commit 7mo ago· 0 open issues

One-line description of what this skill does

Choose how to use this skill

You do not need every option. Choose the path your AI client supports. The stable page stays the same; versioned files are immutable.

1. Native installer

This listing has no registered native installer command. Use the complete package or source fallback below, depending on what your client supports.

Do not guess an installer command or replace an existing version without reviewing the diff.

2. Complete package recommended

Download the ZIP when available. It includes SKILL.md plus the references, security notes and version metadata.

No complete ProSkills package is published for this listing yet.

3. Prompt-only

Copy the prompt above when the agent can read the stable page or when you want to adopt the workflow without installing a skill.

Need only the instruction file?

Download SKILL.md only if your client requires a single file. The complete ZIP is safer for a full installation because it preserves the references and release context.

No path installs or executes anything by itself. Your agent still needs access to the project files. Before updating, compare the installed version and review the diff.

—/10

// RATINGS

⭐GitHub Stars
⭐ 0 on GitHubGitHub ↗

New / niche

🟢ProSkills Score
—
📍

Not yet listed on ClawHub or SkillsMP

// README

Claude Skills & Apps

A curated collection of production-ready skills and apps for Claude Code, Cowork, and compatible AI tools.

What's Inside

This repository is organized into two top-level categories:

Skills

Reusable prompt-based modules that give Claude specialized expertise in a domain. Each skill is a self-contained folder with a SKILL.md and optional supporting files.

DomainDescription
skills/engineering/Development workflows, code review, architecture, debugging
skills/marketing/Content creation, SEO, campaigns, brand voice
skills/product/Specs, roadmaps, sprint planning, research synthesis
skills/operations/Process docs, runbooks, status reports, compliance
skills/data/SQL, analysis, visualization, dashboards
skills/design/UX copy, accessibility, design systems, critique

Apps

Standalone applications, dashboards, and tools built with Claude — ready to run or adapt.

CategoryDescription
apps/dashboards/Interactive HTML/React dashboards and reports
apps/tools/CLI utilities, scripts, and automation tools
apps/automations/Scheduled tasks, workflows, and integrations

Quick Start

Use a skill — copy a skill folder into your Claude Code project or Cowork session:

# Example: use the PR review skill
cp -r skills/engineering/pr-review ~/.claude/commands/

Run an app — follow the README inside each app folder for setup instructions.

Create your own — use the scaffolding script:

# Create a new skill
./scripts/new-skill.sh engineering my-new-skill

# Create a new app
./scripts/new-app.sh tools my-new-app

Skill Structure

Every skill follows this structure:

skills/<domain>/<skill-name>/
├── SKILL.md              # Main skill definition (required)
├── scripts/              # Supporting scripts (optional)
│   └── *.py / *.sh
├── references/           # Frameworks, best practices (optional)
│   └── *.md
└── assets/               # Templates, examples (optional)
    └── *.*

The SKILL.md must include YAML frontmatter:

---
name: Skill Name
description: One-line description of what this skill does
version: "1.0.0"
author: Your Name
tags: [domain, category, keywords]
triggers: [phrases, that, activate, this, skill]
tools_required: [Read, Write, Bash]  # optional
---

App Structure

Every app follows this structure:

apps/<category>/<app-name>/
├── README.md             # Setup, usage, and configuration (required)
├── src/                  # Source code
│   └── *.*
├── assets/               # Static assets (optional)
│   └── *.*
└── tests/                # Tests (optional)
    └── *.*

Contributing

We welcome contributions! Please read CONTRIBUTING.md before submitting.

Key rules:

  • PRs must target the dev branch (PRs to main are auto-closed)
  • Every skill needs a SKILL.md with valid YAML frontmatter
  • Every app needs a README.md with setup instructions
  • No placeholder code — submissions must be production-ready
  • Run ./scripts/lint.sh before submitting

Development

# Clone the repo
git clone https://github.com/smartrus/claude-skills-and-apps.git
cd claude-skills-and-apps

# Create a feature branch from dev
git checkout dev
git checkout -b feat/my-new-skill

# Scaffold a new skill or app
./scripts/new-skill.sh <domain> <name>
./scripts/new-app.sh <category> <name>

# Validate your changes
./scripts/lint.sh

# Push and open a PR against dev
git push -u origin feat/my-new-skill

License

MIT — see LICENSE for details.

// HOW IT'S BUILT

// FILES

2 files shipped with this skill. Inline text is the catalog copy. The upstream link is the source repository.

  • skills/_template/SKILL.md1.1 KBupstream ↗
    ---
    name: "Skill Name"
    description: "One-line description of what this skill does"
    version: "1.0.0"
    author: "Your Name"
    tags: [domain, category, keywords]
    triggers:
      - "phrase that activates this skill"
      - "another trigger phrase"
    tools_required: [Read, Write, Bash]
    ---
    
    # Skill Name
    
    ## Purpose
    
    Describe what this skill does, who it's for, and when to use it.
    
    ## When to Use
    
    - Trigger condition 1
    - Trigger condition 2
    - Trigger condition 3
    
    ## Instructions
    
    <!--
      This is the core prompt that Claude will follow when this skill is activated.
      Write clear, specific instructions. Be opinionated about quality standards.
      Include examples of good output where helpful.
    -->
    
    When activated, follow these steps:
    
    1. **Step 1**: Description of what to do first
    2. **Step 2**: Description of what to do next
    3. **Step 3**: Description of final step
    
    ## Output Format
    
    Describe the expected output format, structure, or deliverable.
    
    ## Examples
    
    ### Input
    ```
    Example user request that would trigger this skill
    ```
    
    ### Output
    ```
    Example of what the skill should produce
    ```
    
    ## References
    
    - Link to relevant documentation or best practices
    
  • README.mdupstream ↗

    Contents are not inlined in the catalog. Open the upstream file.

Plain-text copy, no login: /skill-bundles/smartrus-claude-skills-and-apps-skills-template.md

// REPO STATS

0 stars
0 open issues
Last commit: 7mo ago