convez.ai
SkillAutomaçãoIntermediário
compilet-dev

Uselink Skills para Claude Code

compilet-dev/agent-skill-uselink

Publique docs de engenharia em segundos, compartilháveis sem acesso ao repo

Ver no GitHub
InicialPluginScore · de 0 a 100

Conjunto de skills que automatiza a publicação de artefatos de engenharia (documentação, resumos de repo, digests de PR, changelogs, specs) diretamente para Uselink, gerando URLs compartilháveis sem necessidade de deploy. Cada skill segue o padrão: coleta dados → gera HTML → publica via CLI → retorna link.

Instalação

$npx convez-ai compilet-dev/agent-skill-uselink

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
2
Forks
1
Acompanhando
0
Saúde
50%
Último commit
há 5 meses
Versão
—
Issues abertas
0
Contribuidores
1

Casos de uso

  • Compartilhar resumos de repositório com novos membros do time
  • Gerar e publicar release notes e changelogs automaticamente
  • Criar digests de pull requests para stakeholders
  • Documentar APIs e gerar guias de onboarding
  • Publicar specs de planejamento e relatórios técnicos

Veredito

Skill bem estruturada para automatizar documentação técnica e compartilhamento de artefatos de engenharia. Reduz fricção ao publicar docs geradas por IA, ideal para times que precisam comunicar decisões técnicas rapidamente sem infra complexa.

README

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

Uselink Skills for Claude Code

Agent skills that publish engineering artifacts to uselink -- shareable docs in seconds, no deploy pipeline needed.

Each skill follows the same pattern: gather data -> generate HTML -> publish via CLI -> return shareable link.

What is Uselink?

uselink is a platform for publishing Markdown and HTML to a clean, shareable URL. Paste your AI-generated docs, specs, or reports, publish in seconds, and share the link with stakeholders who can read and comment -- no repo access needed.

Prerequisites

1. Create a Uselink account

Sign up at uselink.app (free tier available -- 3 published docs, no credit card required).

2. Generate an API key

  1. Log in to uselink.app
  2. Go to Settings > API Keys
  3. Click Create API Key
  4. Copy the key (starts with ulk_)

3. Install and configure the CLI

# Install the CLI globally
npm install -g uselink

# Save your API key (interactive prompt)
uselink login

When prompted, paste the API key you copied from step 2.

4. Verify setup

which uselink                # should print a path
cat ~/.uselink/config.json   # should show api_key and api_url

If both commands succeed, you're ready to use the skills.

Installation

Via npx skills (Recommended)

# Install all skills
npx skills add compilet-dev/agent-skill-uselink

# Install a specific skill
npx skills add compilet-dev/agent-skill-uselink --skill uselink-repo-summary

# List available skills
npx skills add compilet-dev/agent-skill-uselink --list

# Install globally (available in all projects)
npx skills add compilet-dev/agent-skill-uselink -g

Via Claude Code (Manual)

git clone https://github.com/compilet-dev/agent-skill-uselink.git
cp -R agent-skill-uselink/skills/* /path/to/your-project/.claude/skills/

Or install from the marketplace manifest:

claude skills install ./marketplace.json

Available Skills

SkillWhat it does
uselink-publishPublish any Markdown or HTML file to uselink
uselink-reportGenerate code review, architecture, or sprint reports and publish
uselink-share-specShare planning specs from .planning/ with stakeholders
uselink-repo-summaryScan a GitHub repo and publish an architecture overview
uselink-pr-digestSummarize a PR as a stakeholder-friendly page and publish
uselink-changelogGenerate release notes from git history and publish
uselink-api-docsScan controllers/routes and publish API documentation
uselink-onboardingGenerate a new-developer onboarding guide and publish

Typical Workflows

1. Share a repo with a new team member

/uselink-repo-summary     -> architecture overview link
/uselink-onboarding       -> getting-started guide link

Send both links -- the new hire reads them before touching the code.

2. Ship a release and notify stakeholders

/uselink-changelog        -> release notes link
/uselink-pr-digest #42    -> detailed PR summary link

Share the changelog in Slack. Link the PR digest for anyone who wants details.

3. Document the API for a partner

/uselink-api-docs         -> API reference link

No Swagger setup, no API gateway. Just scan the code and share.

4. Sprint review

/uselink-report           -> sprint summary with commits, PRs, contributors

Open the link in the meeting. Everyone sees what shipped.

5. Code review for the PM

/uselink-pr-digest #87    -> "what changed and why" page

The PM reads plain English, not diffs.

How Skills Work

Every skill is a SKILL.md file with YAML frontmatter that teaches Claude Code a specific workflow:

1. Check prerequisites (uselink CLI + config)
2. Gather data (git, gh, file reads)
3. Generate HTML (layout-only CSS, no hardcoded colors)
4. Write to /tmp/uselink-<type>-<timestamp>.html
5. Run: uselink publish <file> --title "..." --format html
6. Return the shareable URL

Theme compatibility

Published HTML documents adapt to uselink's light/dark mode automatically. The skill templates use layout-only CSS (padding, margins, borders, border-radius) with no hardcoded background or color. uselink's viewer injects theme-adaptive styles that handle both modes.

Invoke a skill

/uselink-repo-summary
/uselink-changelog
/uselink-pr-digest #42

Or just describe what you want -- Claude matches the right skill:

"Summarize this repo and share it with the PM"
"Generate release notes for this week"
"Create API docs and publish them"

Contributing

  • Each skill is one folder under skills/ with a SKILL.md
  • Skills must check prerequisites before publishing
  • Never set background or color in published HTML -- uselink's viewer handles theming
  • Use opacity for muted text, rgba(128,128,128,0.2) for borders
  • All repo-sourced strings must be HTML-escaped
  • Include a ## Gotchas section with real failure patterns

License

MIT

Ver o original no GitHub

Bom para

Relacionados