convez.ai
MCP Server
shengdabai

Tony-Claude-Code-Skills

shengdabai/Tony-Claude-Code-Skills

Ver no GitHub
BomPluginScore · de 0 a 100

320+ curated Claude Code skills, 9 agents, 39 commands, sanitized configs & a Codex bridge — auto-indexed from skills/.

Instalação

$npx convez-ai shengdabai/Tony-Claude-Code-Skills

1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.

Métricas

Estrelas
3
Forks
1
Acompanhando
1
Saúde
71%
Último commit
há 2 semanas
Versão
—
Issues abertas
2
Contribuidores
4

README

A tradução para o português deste README ainda está na fila.

Tony-Claude-Code-Skills

320+ curated Claude Code skills, 9 agents, 39 commands, sanitized configs & a Codex bridge — auto-indexed from skills/.

Business Context

  • Category: AI workflow infrastructure
  • Audience: AI builders, creators, independent developers, and small teams that want repeatable local AI workflows.
  • Repository status: Public repository. Keep examples, docs, and issues free of credentials, private data, and machine-specific paths.
  • Topics: agents, ai, anthropic, claude-code, codex, developer-tools, llm, mcp, prompt-engineering, skills

What This Project Is For

  • 320+ curated Claude Code skills, 9 agents, 39 commands, sanitized configs & a Codex bridge — auto-indexed from skills/.
  • Package repeatable AI workflows into reusable local assets.
  • Reduce one-off prompt work with versioned skills, guardrails, and handoff files.

Where It Fits

This repository is part of a broader AI local-workbench operating model: reusable skills, local automation, auditable configuration, and repeatable delivery workflows.

Technical Overview

  • Primary language: HTML
  • Detected stack: HTML, Node.js, Python project metadata, Python dependencies, Docker, Docker Compose
  • Default branch: main
  • Visibility: PUBLIC
  • License: MIT License

Repository Map

  • Dockerfile
  • LICENSE
  • NOTICE.md
  • README.md
  • SECURITY.md
  • config
  • install.sh
  • mcp-servers
  • my-config
  • opc-methodology
  • skills
  • tools

Quick Start

Use the commands that match the current project state:

npm install
npm run dev
npm start
npm run build
CommandPurpose
npm installInstall project dependencies.
npm run devbun run browse/src/cli.ts
npm startbun run browse/src/server.ts
npm run buildbun run vendor:xterm && bun run gen:skill-docs --host all; bun build --compile browse/src/cli.ts --outfile...

Operating Notes

  • Keep real credentials out of the repository. Use local environment files, GitHub repository secrets, or the deployment platform secret manager.
  • If a .env.example file exists, treat it as documentation only; never commit filled-in .env files.
  • Before publishing screenshots, demos, or client examples, remove private names, internal paths, account IDs, and API endpoints.
  • The Repository Hygiene workflow is a lightweight guardrail, not a replacement for product-specific tests.

Delivery Checklist

  • README describes the user, business outcome, and operating boundary.
  • Setup or preview commands are current and do not rely on private machine state.
  • No real secrets, private user data, or machine-local state are tracked.
  • Screenshots, demos, or sample outputs are safe to share publicly when the repository is public.
  • Product-specific tests or smoke checks are documented before production use.

Roadmap

  • Tighten the fastest path from clone to useful demo.
  • Add project-specific screenshots, sample outputs, or a short walkthrough where useful.
  • Promote repeated manual steps into scripts, tests, or documented workflows.
  • Keep security, privacy, and licensing boundaries explicit as the project evolves.

Maintainer Notes

Maintained by Tony Sheng. This README is written as a business-facing handoff: it should help a future collaborator, client, or reviewer understand why the repository exists, how to inspect it, and what must be true before it is reused or shipped.

Ver o original no GitHub

Bom para

Relacionados