@fprad0/skill-master-mcp 0.0.9 → 0.0.11

package/docs/operations/GUIA_MULTI_COMPUTADOR.md

@@ -0,0 +1,255 @@
+# Guia Multi-Computador - Skill Master MCP
+
+## 1. Cenario
+
+Voce quer usar o mesmo MCP `skill_master` em varios computadores, mantendo todos atualizados e escolhendo o canal de distribuicao mais adequado para cada caso.
+
+## 2. Modelos recomendados
+
+Hoje existem dois caminhos validos.
+
+### Modelo A - npm publico
+
+Melhor para:
+
+- notebooks novos
+- instalacao rapida
+- ambientes onde o usuario nao deve clonar o repositorio
+- Claude, Codex, Gemini e clientes MCP que aceitam `npx`
+
+Base:
+
+```bash
+npx -y @fprad0/skill-master-mcp@latest
+```
+
+### Modelo B - clone + launcher com auto-update
+
+Melhor para:
+
+- desenvolvimento do MCP
+- testes de `stable` e `beta`
+- controle maior sobre manifests e atualizacao por `git pull --ff-only`
+- ambiente com repo privado
+
+Cada computador tera:
+
+- clone local do repositorio
+- `git`
+- `node` 18+
+- launcher configurado no cliente MCP
+- configuracao local em `%USERPROFILE%/.skill-master/config.json` no Windows ou `~/.skill-master/config.json` no Linux/macOS
+
+Quando o menu detectar que o computador ainda nao esta globalmente pronto, ele vai mostrar o caminho de bootstrap e o atalho unico:
+
+```bash
+skill-master-bootstrap-global
+```
+
+Esse atalho instala as skills globais embutidas e registra Codex, Claude, Gemini e Antigravity para reconhecer `skill_master` como parte do sistema no cliente local.
+
+A partir da correcao multi-OS, o registro recomendado nao depende mais de `PATH`. O registrador grava o Node.js absoluto como `command` e o `bin/skill-master.mjs` absoluto como `args`, o que evita falhas comuns em Windows, Linux, macOS e apps desktop que nao herdam o ambiente do terminal.
+
+A partir da preparacao `0.0.11`, use o doctor para validar notebooks novos:
+
+```bash
+skill-master-menu --run doctor
+skill-master-menu --run bootstrap-global --yes
+```
+
+O bootstrap registra Codex, Claude Desktop, Gemini CLI e Antigravity. Depois, reinicie os clientes.
+
+## 3. Instalacao em um novo computador
+
+### 3.1 Opcao rapida - npm publico
+
+#### Windows
+
+```powershell
+npm install -g @fprad0/skill-master-mcp
+```
+
+ou:
+
+```powershell
+npx -y @fprad0/skill-master-mcp@latest
+```
+
+#### Linux / macOS
+
+```bash
+npm install -g @fprad0/skill-master-mcp
+```
+
+ou:
+
+```bash
+npx -y @fprad0/skill-master-mcp@latest
+```
+
+### 3.2 Opcao controlada - clone local
+
+Pre-requisitos:
+
+- Git instalado
+- Node.js 18+
+- acesso ao GitHub
+- token read-only se o repositorio for privado
+
+Clone:
+
+```powershell
+cd C:\Users\CDT\Documents
+git clone https://github.com/FPrad0/skill-master-mcp.git
+cd skill-master-mcp
+npm ci
+npm run build
+```
+
+### 3.3 Configuracao local
+
+Criar:
+
+```text
+C:\Users\<USER>\.skill-master\config.json
+```
+
+Modelo:
+
+```json
+{
+  "channel": "stable",
+  "autoUpdate": true,
+  "updateMode": "on-start",
+  "manifestUrl": "https://raw.githubusercontent.com/FPrad0/skill-master-mcp/main/manifests/channels/stable.json",
+  "localSkillRoots": [
+    "%USERPROFILE%/.codex/skills",
+    "%USERPROFILE%/.agents/skills"
+  ],
+  "allowWebSources": false
+}
+```
+
+## 4. Configuracao do cliente MCP
+
+No modelo npm global, prefira sempre o registro gerado por `skill-master-register-clients`, porque ele usa caminhos absolutos.
+
+No modelo clone + launcher, o launcher ainda e valido para desenvolvimento, mas o doctor vai classificar esse modo como `launcher`, nao como o modo robusto de pacote global.
+
+Exemplo robusto para Codex:
+
+```toml
+[mcp_servers.skill_master]
+command = "C:\\Program Files\\nodejs\\node.exe"
+args = ["C:\\Users\\CDT\\AppData\\Roaming\\npm\\node_modules\\@fprad0\\skill-master-mcp\\bin\\skill-master.mjs"]
+startup_timeout_sec = 120
+
+[mcp_servers.skill_master.env]
+SKILL_MASTER_UPDATE_CHANNEL = "stable"
+```
+
+Para migrar clientes antigos que ainda usam `skill-master-mcp` via PATH, `npx` ou launcher local:
+
+```bash
+skill-master-register-clients --apply-all --force
+skill-master-menu --run doctor
+```
+
+No modelo clone + launcher, o cliente deve chamar o launcher, nao o `dist/index.js` diretamente.
+
+Exemplo conceitual:
+
+```json
+{
+  "mcpServers": {
+    "skill_master": {
+      "command": "powershell",
+      "args": [
+        "-ExecutionPolicy",
+        "Bypass",
+        "-File",
+        "C:/Users/CDT/Documents/skill-master-mcp/scripts/skill-master-launcher.ps1"
+      ]
+    }
+  }
+}
+```
+
+## 5. Como as atualizacoes chegam automaticamente
+
+### No modelo npm publico
+
+1. voce publica uma nova versao no npm publico
+2. a maquina cliente usa `@latest`
+3. no proximo `npx` ou reinstalacao, a nova versao e resolvida
+
+### No modelo clone + launcher
+
+1. voce faz push no GitHub
+2. voce atualiza o manifesto `stable.json`
+3. o usuario abre o MCP
+4. o launcher verifica o manifesto
+5. se houver versao nova e o clone local estiver limpo, o launcher atualiza
+6. o MCP inicia ja atualizado
+
+## 6. Como publicar uma atualizacao
+
+### Caminho publico
+
+1. subir a nova versao para `main`
+2. publicar pelo workflow `Publish Skill Master to npmjs` somente com autorizacao explicita
+3. validar com `npm view` e `npx`
+
+### Caminho clone + launcher
+
+1. subir a nova versao para `main`
+2. atualizar `manifests/channels/stable.json`
+3. criar release/tag quando fizer sentido
+4. deixar o launcher puxar com `git pull --ff-only`
+
+## 7. Estrategia para varios usuarios
+
+### Poucos usuarios tecnicos
+
+Use clone privado + launcher. E a rota com mais controle.
+
+### Varios usuarios sem perfil tecnico
+
+Use npm publico.
+
+Se for necessario restringir distribuicao, evolua para:
+
+- pacote npm privado
+- instalador/bundle
+- MCP remoto
+
+### Equipe ou empresa
+
+Evoluir para:
+
+- GitHub Packages com permissoes
+- workflow de release
+- canais `stable` e `beta`
+- logs e telemetria minima opcional
+
+## 8. Manutencao
+
+Recomendacoes:
+
+- manter changelog curto
+- nunca quebrar configuracao sem migracao
+- testar update em uma maquina secundaria antes de mover `stable`
+- manter `beta` para validacao
+- documentar breaking changes
+
+## 9. Quando nao atualizar automaticamente
+
+No modelo clone + launcher, o updater deve recusar atualizacao automatica quando:
+
+- houver arquivos locais modificados
+- o GitHub estiver inacessivel
+- o manifesto estiver invalido
+- houver mudanca de versao de Node nao atendida
+- `npm ci` ou build falhar
+
+Nesses casos, ele deve iniciar a versao local e mostrar o status pela ferramenta `skill_master_sync_status`.

package/docs/operations/GUIA_NPM_PUBLICO.md

@@ -0,0 +1,147 @@
+# Guia de Publicacao no npm Publico
+
+## Objetivo
+
+Distribuir o `skill_master` pelo `npmjs.org`, permitindo instalacao direta com:
+
+```bash
+npm install -g @fprad0/skill-master-mcp
+```
+
+ou execucao imediata com:
+
+```bash
+npx -y @fprad0/skill-master-mcp@latest
+```
+
+## Estado atual
+
+Em `2026-06-26`, o pacote:
+
+- ja esta funcional no GitHub Packages privado
+- ja esta publicado no `registry.npmjs.org`
+- ja responde em `npm view @fprad0/skill-master-mcp --registry=https://registry.npmjs.org`
+- ja pode ser instalado com `npm install -g @fprad0/skill-master-mcp`
+- ja pode ser executado com `npx -y @fprad0/skill-master-mcp@latest`
+
+Versao publica validada:
+
+- `0.0.2`
+
+Workflow de referencia:
+
+- `Publish Skill Master to npmjs`
+- run `28244958247`
+- status `success`
+
+## O que isso habilita na pratica
+
+Para uma maquina nova, o caminho mais simples agora e:
+
+```bash
+npm install -g @fprad0/skill-master-mcp
+```
+
+Se a ideia for testar sem install global:
+
+```bash
+npx -y @fprad0/skill-master-mcp@latest
+```
+
+## Validacoes locais recomendadas
+
+### Confirmar login no npmjs
+
+```bash
+npm whoami
+```
+
+### Verificar a versao publicada
+
+```bash
+npm view @fprad0/skill-master-mcp version --registry=https://registry.npmjs.org
+```
+
+### Verificar dist-tags
+
+```bash
+npm view @fprad0/skill-master-mcp dist-tags --json --registry=https://registry.npmjs.org
+```
+
+### Smoke test via npx
+
+```bash
+npx -y @fprad0/skill-master-mcp@latest
+```
+
+## Publicacao local manual
+
+Com login valido no npmjs:
+
+```bash
+npm run publish:npm-public
+```
+
+Esse script publica com:
+
+```bash
+npm publish --access public --registry=https://registry.npmjs.org
+```
+
+## Publicacao por GitHub Actions
+
+O repositorio possui o workflow:
+
+```text
+Publish Skill Master to npmjs
+```
+
+Pre-requisitos:
+
+- secret `NPM_TOKEN` configurado no GitHub
+- token com permissao de publicacao na conta/escopo correto
+- versao do `package.json` ainda nao publicada no npm publico
+
+Fluxo:
+
+1. abrir `Actions` no GitHub
+2. escolher `Publish Skill Master to npmjs`
+3. informar o `ref` a publicar, por exemplo `main` ou uma tag
+4. executar o workflow
+
+O workflow faz:
+
+- `npm ci`
+- `npm run build`
+- `npm test`
+- `npm run check:manifest`
+- `npm run publish:npm-public`
+
+## Riscos e limites
+
+- publicacao no npm publico e visivel publicamente
+- nao e possivel republicar a mesma versao
+- antes de cada novo publish, confirme nome, escopo, metadados e estrategia de suporte
+- o fluxo privado no GitHub Packages continua valido para distribuicao fechada ou controlada
+
+## Checklist rapido depois da release
+
+```bash
+npm view @fprad0/skill-master-mcp version --registry=https://registry.npmjs.org
+```
+
+```bash
+npm view @fprad0/skill-master-mcp dist-tags --json --registry=https://registry.npmjs.org
+```
+
+```bash
+npx -y @fprad0/skill-master-mcp@latest
+```
+
+Se quiser validar instalacao limpa:
+
+```bash
+mkdir skill-master-smoke && cd skill-master-smoke
+npm init -y
+npm install @fprad0/skill-master-mcp --registry=https://registry.npmjs.org
+```

package/docs/skill-candidates/v0.0.10/cli-creator/LICENSE.txt

@@ -0,0 +1,201 @@
+Apache License
+Version 2.0, January 2004
+http://www.apache.org/licenses/
+
+TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+1. Definitions.
+
+   "License" shall mean the terms and conditions for use, reproduction,
+   and distribution as defined by Sections 1 through 9 of this document.
+
+   "Licensor" shall mean the copyright owner or entity authorized by
+   the copyright owner that is granting the License.
+
+   "Legal Entity" shall mean the union of the acting entity and all
+   other entities that control, are controlled by, or are under common
+   control with that entity. For the purposes of this definition,
+   "control" means (i) the power, direct or indirect, to cause the
+   direction or management of such entity, whether by contract or
+   otherwise, or (ii) ownership of fifty percent (50%) or more of the
+   outstanding shares, or (iii) beneficial ownership of such entity.
+
+   "You" (or "Your") shall mean an individual or Legal Entity
+   exercising permissions granted by this License.
+
+   "Source" form shall mean the preferred form for making modifications,
+   including but not limited to software source code, documentation
+   source, and configuration files.
+
+   "Object" form shall mean any form resulting from mechanical
+   transformation or translation of a Source form, including but
+   not limited to compiled object code, generated documentation,
+   and conversions to other media types.
+
+   "Work" shall mean the work of authorship, whether in Source or
+   Object form, made available under the License, as indicated by a
+   copyright notice that is included in or attached to the work
+   (an example is provided in the Appendix below).
+
+   "Derivative Works" shall mean any work, whether in Source or Object
+   form, that is based on (or derived from) the Work and for which the
+   editorial revisions, annotations, elaborations, or other modifications
+   represent, as a whole, an original work of authorship. For the purposes
+   of this License, Derivative Works shall not include works that remain
+   separable from, or merely link (or bind by name) to the interfaces of,
+   the Work and Derivative Works thereof.
+
+   "Contribution" shall mean any work of authorship, including
+   the original version of the Work and any modifications or additions
+   to that Work or Derivative Works thereof, that is intentionally
+   submitted to Licensor for inclusion in the Work by the copyright owner
+   or by an individual or Legal Entity authorized to submit on behalf of
+   the copyright owner. For the purposes of this definition, "submitted"
+   means any form of electronic, verbal, or written communication sent
+   to the Licensor or its representatives, including but not limited to
+   communication on electronic mailing lists, source code control systems,
+   and issue tracking systems that are managed by, or on behalf of, the
+   Licensor for the purpose of discussing and improving the Work, but
+   excluding communication that is conspicuously marked or otherwise
+   designated in writing by the copyright owner as "Not a Contribution."
+
+   "Contributor" shall mean Licensor and any individual or Legal Entity
+   on behalf of whom a Contribution has been received by Licensor and
+   subsequently incorporated within the Work.
+
+2. Grant of Copyright License. Subject to the terms and conditions of
+   this License, each Contributor hereby grants to You a perpetual,
+   worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+   copyright license to reproduce, prepare Derivative Works of,
+   publicly display, publicly perform, sublicense, and distribute the
+   Work and such Derivative Works in Source or Object form.
+
+3. Grant of Patent License. Subject to the terms and conditions of
+   this License, each Contributor hereby grants to You a perpetual,
+   worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+   (except as stated in this section) patent license to make, have made,
+   use, offer to sell, sell, import, and otherwise transfer the Work,
+   where such license applies only to those patent claims licensable
+   by such Contributor that are necessarily infringed by their
+   Contribution(s) alone or by combination of their Contribution(s)
+   with the Work to which such Contribution(s) was submitted. If You
+   institute patent litigation against any entity (including a
+   cross-claim or counterclaim in a lawsuit) alleging that the Work
+   or a Contribution incorporated within the Work constitutes direct
+   or contributory patent infringement, then any patent licenses
+   granted to You under this License for that Work shall terminate
+   as of the date such litigation is filed.
+
+4. Redistribution. You may reproduce and distribute copies of the
+   Work or Derivative Works thereof in any medium, with or without
+   modifications, and in Source or Object form, provided that You
+   meet the following conditions:
+
+   (a) You must give any other recipients of the Work or
+       Derivative Works a copy of this License; and
+
+   (b) You must cause any modified files to carry prominent notices
+       stating that You changed the files; and
+
+   (c) You must retain, in the Source form of any Derivative Works
+       that You distribute, all copyright, patent, trademark, and
+       attribution notices from the Source form of the Work,
+       excluding those notices that do not pertain to any part of
+       the Derivative Works; and
+
+   (d) If the Work includes a "NOTICE" text file as part of its
+       distribution, then any Derivative Works that You distribute must
+       include a readable copy of the attribution notices contained
+       within such NOTICE file, excluding those notices that do not
+       pertain to any part of the Derivative Works, in at least one
+       of the following places: within a NOTICE text file distributed
+       as part of the Derivative Works; within the Source form or
+       documentation, if provided along with the Derivative Works; or,
+       within a display generated by the Derivative Works, if and
+       wherever such third-party notices normally appear. The contents
+       of the NOTICE file are for informational purposes only and
+       do not modify the License. You may add Your own attribution
+       notices within Derivative Works that You distribute, alongside
+       or as an addendum to the NOTICE text from the Work, provided
+       that such additional attribution notices cannot be construed
+       as modifying the License.
+
+   You may add Your own copyright statement to Your modifications and
+   may provide additional or different license terms and conditions
+   for use, reproduction, or distribution of Your modifications, or
+   for any such Derivative Works as a whole, provided Your use,
+   reproduction, and distribution of the Work otherwise complies with
+   the conditions stated in this License.
+
+5. Submission of Contributions. Unless You explicitly state otherwise,
+   any Contribution intentionally submitted for inclusion in the Work
+   by You to the Licensor shall be under the terms and conditions of
+   this License, without any additional terms or conditions.
+   Notwithstanding the above, nothing herein shall supersede or modify
+   the terms of any separate license agreement you may have executed
+   with Licensor regarding such Contributions.
+
+6. Trademarks. This License does not grant permission to use the trade
+   names, trademarks, service marks, or product names of the Licensor,
+   except as required for reasonable and customary use in describing the
+   origin of the Work and reproducing the content of the NOTICE file.
+
+7. Disclaimer of Warranty. Unless required by applicable law or
+   agreed to in writing, Licensor provides the Work (and each
+   Contributor provides its Contributions) on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+   implied, including, without limitation, any warranties or conditions
+   of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+   PARTICULAR PURPOSE. You are solely responsible for determining the
+   appropriateness of using or redistributing the Work and assume any
+   risks associated with Your exercise of permissions under this License.
+
+8. Limitation of Liability. In no event and under no legal theory,
+   whether in tort (including negligence), contract, or otherwise,
+   unless required by applicable law (such as deliberate and grossly
+   negligent acts) or agreed to in writing, shall any Contributor be
+   liable to You for damages, including any direct, indirect, special,
+   incidental, or consequential damages of any character arising as a
+   result of this License or out of the use or inability to use the
+   Work (including but not limited to damages for loss of goodwill,
+   work stoppage, computer failure or malfunction, or any and all
+   other commercial damages or losses), even if such Contributor
+   has been advised of the possibility of such damages.
+
+9. Accepting Warranty or Additional Liability. While redistributing
+   the Work or Derivative Works thereof, You may choose to offer,
+   and charge a fee for, acceptance of support, warranty, indemnity,
+   or other liability obligations and/or rights consistent with this
+   License. However, in accepting such obligations, You may act only
+   on Your own behalf and on Your sole responsibility, not on behalf of
+   any other Contributor, and only if You agree to indemnify,
+   defend, and hold each Contributor harmless for any liability
+   incurred by, or claims asserted against, such Contributor by reason
+   of your accepting any such warranty or additional liability.
+
+END OF TERMS AND CONDITIONS
+
+APPENDIX: How to apply the Apache License to your work.
+
+   To apply the Apache License to your work, attach the following
+   boilerplate notice, with the fields enclosed by brackets "[]"
+   replaced with your own identifying information. (Don\'t include
+   the brackets!)  The text should be enclosed in the appropriate
+   comment syntax for the file format. We also recommend that a
+   file or class name and description of purpose be included on the
+   same "printed page" as the copyright notice for easier
+   identification within third-party archives.
+
+Copyright [yyyy] [name of copyright owner]
+
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
+
+    http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.