jorgex-stack 1.1.1 → 1.2.0

package/stack/skills/mcp-builder/reference/evaluation.md

@@ -381,16 +381,13 @@ After creating your evaluation file, you can use the provided evaluation harness
 
 ## Setup
 
-1. **Install Dependencies**
+1. **Prepare a locked Python environment**
 
-   ```bash
-   pip install -r scripts/requirements.txt
-   ```
-
-   Or install manually:
-   ```bash
-   pip install anthropic mcp
-   ```
+   Use a project-managed virtual environment whose complete transitive lock and
+   hashes have already been reviewed. The requirements file records the direct
+   versions expected by the harness, but it is not a complete lock and this
+   skill must not install from it. If the environment is unavailable, stop and
+   return control to the user.
 
 2. **Set API Key**
 
@@ -550,12 +547,8 @@ Here's a complete example of creating and running an evaluation:
 </evaluation>
 ```
 
-2. **Install dependencies**:
-
-```bash
-pip install -r scripts/requirements.txt
-export ANTHROPIC_API_KEY=your_api_key
-```
+2. **Activate the pre-provisioned locked environment**, then provide the API key
+   through the project's normal secret-management workflow.
 
 3. **Run evaluation**:
 
@@ -599,4 +592,4 @@ If tasks are timing out:
 - Use a more capable model (e.g., `claude-3-7-sonnet-20250219`)
 - Check if tools are returning too much data
 - Verify pagination is working correctly
-- Consider simplifying complex questions
+- Consider simplifying complex questions

package/stack/skills/mcp-builder/reference/node_mcp_server.md

@@ -901,16 +901,19 @@ Always build your TypeScript code before running:
 
 ```bash
 # Build the project
-npm run build
+pnpm run build
 
 # Run the server
-npm start
+pnpm start
 
 # Development with auto-reload
-npm run dev
+pnpm run dev
 ```
 
-Always ensure `npm run build` completes successfully before considering the implementation complete.
+Always ensure `pnpm run build` completes successfully before considering the
+implementation complete. These commands must resolve the project's declared
+dependencies through its lockfile; do not fetch an unpinned tool while
+working on the server.
 
 ## Quality Checklist
 
@@ -963,8 +966,8 @@ Before finalizing your Node/TypeScript MCP server implementation, ensure:
 - [ ] Return types are consistent across similar operations
 
 ### Testing and Build
-- [ ] `npm run build` completes successfully without errors
+- [ ] `pnpm run build` completes successfully without errors
 - [ ] dist/index.js created and executable
 - [ ] Server runs: `node dist/index.js --help`
 - [ ] All imports resolve correctly
-- [ ] Sample tool calls work as expected
+- [ ] Sample tool calls work as expected

package/stack/skills/mcp-builder/scripts/requirements.txt

@@ -1,2 +1,2 @@
-anthropic>=0.39.0
-mcp>=1.1.0
+anthropic==0.39.0
+mcp==1.1.0

package/stack/skills/playwright-cli/references/test-generation.md

@@ -153,11 +153,10 @@ test -f playwright.config.ts || test -f playwright.config.js
 pnpm exec playwright --version
 ```
 
-If there is no Playwright install, bootstrap one and let the user pick the defaults:
-
-```bash
-pnpm create playwright
-```
+If there is no project-local Playwright install, stop and return control to the
+user. This skill does not bootstrap packages or change the dependency graph;
+the project must provision a reviewed exact version through its normal locked
+dependency workflow before planning or generating tests.
 
 ### 1.2 Prerequisite: seed test
 

package/stack/skills/react-doctor/SKILL.md

@@ -10,10 +10,21 @@ Scans your React codebase for security, performance, correctness, and architectu
 
 ## Usage
 
+Run the project-pinned binary through the project's package manager:
+
 ```bash
-npx -y react-doctor@latest . --verbose --diff
+pnpm exec react-doctor . --verbose --diff
 ```
 
+`pnpm exec` resolves the binary from the current project's declared
+dependencies or workspace. It does not fetch an ad-hoc release and this skill
+does not modify `package.json`, the lockfile, or any global tool directory.
+
+If the command is unavailable, stop and return control to the user with a
+clear message that the project dependency is missing. The user can review and
+provision an exact project version through the normal dependency workflow,
+then rerun this skill.
+
 ## Workflow
 
 Run after making changes to catch issues early. Fix errors first, then re-run to verify the score improved.

package/upstreams.json

@@ -1,5 +1,5 @@
 {
-  "$comment": "Terceros gestionados por `jorgex-stack update`: fuente, versión conocida y política. `commit` = pin del upstream en la última revisión aceptada (2026-06-11, auditoría de seguridad): update --check compara el HEAD del repo contra el pin y avisa si se movió; cualquier actualización de la copia vendorizada se hace con diff manual y re-pin deliberado, nunca a ciegas. El pin es del repo completo (no por path): en monorepos activos un pin movido no implica que la skill cambiara — el diff lo confirma. Las skills 'modified: true' tienen cambios locales respecto al upstream — update debe hacer diff/aviso, NUNCA reemplazo ciego (PRD §7.3). Skills propias sin upstream (no se actualizan desde fuera): agent-delegation, work-lifecycle. `path` = ruta dentro del repo upstream donde vive la skill (para diff/descarga quirúrgica). `kind: \"release\"` = la actualización se compara contra tags de release en vez de HEAD (e.g. paquetes Python sin SKILL.md en repo).",
+  "$comment": "Terceros gestionados por `jorgex-stack update`: fuente, versión conocida y política. `commit` = pin del upstream en la última revisión aceptada (2026-06-11, auditoría de seguridad): update --check compara el HEAD del repo contra el pin y avisa si se movió; cualquier actualización de la copia vendorizada se hace con diff manual y re-pin deliberado, nunca a ciegas. El pin es del repo completo (no por path): en monorepos activos un pin movido no implica que la skill cambiara — el diff lo confirma. Las skills 'modified: true' tienen cambios locales respecto al upstream — update debe hacer diff/aviso, NUNCA reemplazo ciego (PRD §7.3). Skills propias sin upstream (no se actualizan desde fuera): agent-delegation, lean-code, orchestrator, work-lifecycle y xreview. `path` = ruta dentro del repo upstream donde vive la skill (para diff/descarga quirúrgica). `kind: \"release\"` = la actualización se compara contra tags de release en vez de HEAD (e.g. paquetes Python sin SKILL.md en repo).",
   "tools": {
     "engram": {
       "kind": "binary",
@@ -24,6 +24,7 @@
       "path": "skills/deploy-to-vercel",
       "version": "3.0.0",
       "commit": "f8a72b9603728bb92a217a879b7e62e43ad76c81",
+      "modified": true,
       "note": "por diseño empaqueta el proyecto entero (tarball) y lo sube a un endpoint de Vercel para desplegarlo; excluye .env/.env.*/.git/node_modules"
     },
     "diagnose": {
@@ -35,46 +36,43 @@
     "find-skills": {
       "source": "github:vercel-labs/skills",
       "path": "skills/find-skills",
-      "commit": "be0dd25b4a8665894a56f45ef582cc02ca802c39"
+      "commit": "be0dd25b4a8665894a56f45ef582cc02ca802c39",
+      "modified": true,
+      "note": "la copia vendorizada se limita a descubrir skills; no acepta ni ejecuta instalación, actualización o inicialización de contenido upstream"
     },
     "mcp-builder": {
       "source": "github:anthropics/skills",
       "path": "skills/mcp-builder",
       "commit": "57546260929473d4e0d1c1bb75297be2fdfa1949",
-      "license": "Apache-2.0"
-    },
-    "obsidian-cli": {
-      "source": "github:kepano/obsidian-skills",
-      "path": "skills/obsidian-cli",
-      "commit": "a1dc48e68138490d522c04cbf5822214c6eb1202"
-    },
-    "obsidian-markdown": {
-      "source": "github:kepano/obsidian-skills",
-      "path": "skills/obsidian-markdown",
-      "commit": "a1dc48e68138490d522c04cbf5822214c6eb1202"
+      "license": "Apache-2.0",
+      "modified": true
     },
     "react-doctor": {
       "source": "github:millionco/react-doctor",
       "path": "skills/react-doctor",
-      "commit": "a48fb06ffbe7221655e18529fcc954ecae17a22f"
+      "commit": "a48fb06ffbe7221655e18529fcc954ecae17a22f",
+      "modified": true
     },
     "skill-creator": {
       "source": "github:anthropics/skills",
       "path": "skills/skill-creator",
       "commit": "57546260929473d4e0d1c1bb75297be2fdfa1949",
-      "license": "Apache-2.0"
+      "license": "Apache-2.0",
+      "modified": true
     },
     "supabase": {
       "source": "github:supabase/agent-skills",
       "path": "skills/supabase",
       "version": "0.1.2",
-      "commit": "1356046015476711a769601079262b5635929427"
+      "commit": "1356046015476711a769601079262b5635929427",
+      "modified": true
     },
     "supabase-postgres-best-practices": {
       "source": "github:supabase/agent-skills",
       "path": "skills/supabase-postgres-best-practices",
       "commit": "1356046015476711a769601079262b5635929427",
-      "license": "MIT"
+      "license": "MIT",
+      "modified": true
     },
     "tdd": {
       "source": "github:mattpocock/skills",
@@ -84,14 +82,17 @@
     },
     "to-issues": {
       "source": "github:mattpocock/skills",
-      "path": "skills/engineering/to-issues",
-      "commit": "694fa30311e02c2639942308513555e61ee84a6f"
+      "path": "skills/engineering/to-tickets",
+      "commit": "694fa30311e02c2639942308513555e61ee84a6f",
+      "modified": true,
+      "note": "upstream renombró to-issues → to-tickets; conservamos el nombre local to-issues y el pin de la última revisión aceptada hasta comparar y aceptar contenido nuevo deliberadamente"
     },
     "to-prd": {
       "source": "github:mattpocock/skills",
-      "path": "skills/engineering/to-prd",
+      "path": "skills/engineering/to-spec",
       "commit": "694fa30311e02c2639942308513555e61ee84a6f",
-      "modified": true
+      "modified": true,
+      "note": "upstream renombró to-prd → to-spec; conservamos el nombre local to-prd y el pin de la última revisión aceptada hasta comparar y aceptar contenido nuevo deliberadamente"
     }
   }
 }

package/stack/skills/obsidian-cli/SKILL.md

@@ -1,106 +0,0 @@
----
-name: obsidian-cli
-description: Interact with Obsidian vaults using the Obsidian CLI to read, create, search, and manage notes, tasks, properties, and more. Also supports plugin and theme development with commands to reload plugins, run JavaScript, capture errors, take screenshots, and inspect the DOM. Use when the user asks to interact with their Obsidian vault, manage notes, search vault content, perform vault operations from the command line, or develop and debug Obsidian plugins and themes.
----
-
-# Obsidian CLI
-
-Use the `obsidian` CLI to interact with a running Obsidian instance. Requires Obsidian to be open.
-
-## Command reference
-
-Run `obsidian help` to see all available commands. This is always up to date. Full docs: https://help.obsidian.md/cli
-
-## Syntax
-
-**Parameters** take a value with `=`. Quote values with spaces:
-
-```bash
-obsidian create name="My Note" content="Hello world"
-```
-
-**Flags** are boolean switches with no value:
-
-```bash
-obsidian create name="My Note" silent overwrite
-```
-
-For multiline content use `\n` for newline and `\t` for tab.
-
-## File targeting
-
-Many commands accept `file` or `path` to target a file. Without either, the active file is used.
-
-- `file=<name>` — resolves like a wikilink (name only, no path or extension needed)
-- `path=<path>` — exact path from vault root, e.g. `folder/note.md`
-
-## Vault targeting
-
-Commands target the most recently focused vault by default. Use `vault=<name>` as the first parameter to target a specific vault:
-
-```bash
-obsidian vault="My Vault" search query="test"
-```
-
-## Common patterns
-
-```bash
-obsidian read file="My Note"
-obsidian create name="New Note" content="# Hello" template="Template" silent
-obsidian append file="My Note" content="New line"
-obsidian search query="search term" limit=10
-obsidian daily:read
-obsidian daily:append content="- [ ] New task"
-obsidian property:set name="status" value="done" file="My Note"
-obsidian tasks daily todo
-obsidian tags sort=count counts
-obsidian backlinks file="My Note"
-```
-
-Use `--copy` on any command to copy output to clipboard. Use `silent` to prevent files from opening. Use `total` on list commands to get a count.
-
-## Plugin development
-
-### Develop/test cycle
-
-After making code changes to a plugin or theme, follow this workflow:
-
-1. **Reload** the plugin to pick up changes:
-   ```bash
-   obsidian plugin:reload id=my-plugin
-   ```
-2. **Check for errors** — if errors appear, fix and repeat from step 1:
-   ```bash
-   obsidian dev:errors
-   ```
-3. **Verify visually** with a screenshot or DOM inspection:
-   ```bash
-   obsidian dev:screenshot path=screenshot.png
-   obsidian dev:dom selector=".workspace-leaf" text
-   ```
-4. **Check console output** for warnings or unexpected logs:
-   ```bash
-   obsidian dev:console level=error
-   ```
-
-### Additional developer commands
-
-Run JavaScript in the app context:
-
-```bash
-obsidian eval code="app.vault.getFiles().length"
-```
-
-Inspect CSS values:
-
-```bash
-obsidian dev:css selector=".workspace-leaf" prop=background-color
-```
-
-Toggle mobile emulation:
-
-```bash
-obsidian dev:mobile on
-```
-
-Run `obsidian help` to see additional developer commands including CDP and debugger controls.

package/stack/skills/obsidian-markdown/SKILL.md

@@ -1,196 +0,0 @@
----
-name: obsidian-markdown
-description: Create and edit Obsidian Flavored Markdown with wikilinks, embeds, callouts, properties, and other Obsidian-specific syntax. Use when working with .md files in Obsidian, or when the user mentions wikilinks, callouts, frontmatter, tags, embeds, or Obsidian notes.
----
-
-# Obsidian Flavored Markdown Skill
-
-Create and edit valid Obsidian Flavored Markdown. Obsidian extends CommonMark and GFM with wikilinks, embeds, callouts, properties, comments, and other syntax. This skill covers only Obsidian-specific extensions -- standard Markdown (headings, bold, italic, lists, quotes, code blocks, tables) is assumed knowledge.
-
-## Workflow: Creating an Obsidian Note
-
-1. **Add frontmatter** with properties (title, tags, aliases) at the top of the file. See [PROPERTIES.md](references/PROPERTIES.md) for all property types.
-2. **Write content** using standard Markdown for structure, plus Obsidian-specific syntax below.
-3. **Link related notes** using wikilinks (`[[Note]]`) for internal vault connections, or standard Markdown links for external URLs.
-4. **Embed content** from other notes, images, or PDFs using the `![[embed]]` syntax. See [EMBEDS.md](references/EMBEDS.md) for all embed types.
-5. **Add callouts** for highlighted information using `> [!type]` syntax. See [CALLOUTS.md](references/CALLOUTS.md) for all callout types.
-6. **Verify** the note renders correctly in Obsidian's reading view.
-
-> When choosing between wikilinks and Markdown links: use `[[wikilinks]]` for notes within the vault (Obsidian tracks renames automatically) and `[text](url)` for external URLs only.
-
-## Internal Links (Wikilinks)
-
-```markdown
-[[Note Name]]                          Link to note
-[[Note Name|Display Text]]             Custom display text
-[[Note Name#Heading]]                  Link to heading
-[[Note Name#^block-id]]                Link to block
-[[#Heading in same note]]              Same-note heading link
-```
-
-Define a block ID by appending `^block-id` to any paragraph:
-
-```markdown
-This paragraph can be linked to. ^my-block-id
-```
-
-For lists and quotes, place the block ID on a separate line after the block:
-
-```markdown
-> A quote block
-
-^quote-id
-```
-
-## Embeds
-
-Prefix any wikilink with `!` to embed its content inline:
-
-```markdown
-![[Note Name]]                         Embed full note
-![[Note Name#Heading]]                 Embed section
-![[image.png]]                         Embed image
-![[image.png|300]]                     Embed image with width
-![[document.pdf#page=3]]               Embed PDF page
-```
-
-See [EMBEDS.md](references/EMBEDS.md) for audio, video, search embeds, and external images.
-
-## Callouts
-
-```markdown
-> [!note]
-> Basic callout.
-
-> [!warning] Custom Title
-> Callout with a custom title.
-
-> [!faq]- Collapsed by default
-> Foldable callout (- collapsed, + expanded).
-```
-
-Common types: `note`, `tip`, `warning`, `info`, `example`, `quote`, `bug`, `danger`, `success`, `failure`, `question`, `abstract`, `todo`.
-
-See [CALLOUTS.md](references/CALLOUTS.md) for the full list with aliases, nesting, and custom CSS callouts.
-
-## Properties (Frontmatter)
-
-```yaml
----
-title: My Note
-date: 2024-01-15
-tags:
-  - project
-  - active
-aliases:
-  - Alternative Name
-cssclasses:
-  - custom-class
----
-```
-
-Default properties: `tags` (searchable labels), `aliases` (alternative note names for link suggestions), `cssclasses` (CSS classes for styling).
-
-See [PROPERTIES.md](references/PROPERTIES.md) for all property types, tag syntax rules, and advanced usage.
-
-## Tags
-
-```markdown
-#tag                    Inline tag
-#nested/tag             Nested tag with hierarchy
-```
-
-Tags can contain letters, numbers (not first character), underscores, hyphens, and forward slashes. Tags can also be defined in frontmatter under the `tags` property.
-
-## Comments
-
-```markdown
-This is visible %%but this is hidden%% text.
-
-%%
-This entire block is hidden in reading view.
-%%
-```
-
-## Obsidian-Specific Formatting
-
-```markdown
-==Highlighted text==                   Highlight syntax
-```
-
-## Math (LaTeX)
-
-```markdown
-Inline: $e^{i\pi} + 1 = 0$
-
-Block:
-$$
-\frac{a}{b} = c
-$$
-```
-
-## Diagrams (Mermaid)
-
-````markdown
-```mermaid
-graph TD
-    A[Start] --> B{Decision}
-    B -->|Yes| C[Do this]
-    B -->|No| D[Do that]
-```
-````
-
-To link Mermaid nodes to Obsidian notes, add `class NodeName internal-link;`.
-
-## Footnotes
-
-```markdown
-Text with a footnote[^1].
-
-[^1]: Footnote content.
-
-Inline footnote.^[This is inline.]
-```
-
-## Complete Example
-
-````markdown
----
-title: Project Alpha
-date: 2024-01-15
-tags:
-  - project
-  - active
-status: in-progress
----
-
-# Project Alpha
-
-This project aims to [[improve workflow]] using modern techniques.
-
-> [!important] Key Deadline
-> The first milestone is due on ==January 30th==.
-
-## Tasks
-
-- [x] Initial planning
-- [ ] Development phase
-  - [ ] Backend implementation
-  - [ ] Frontend design
-
-## Notes
-
-The algorithm uses $O(n \log n)$ sorting. See [[Algorithm Notes#Sorting]] for details.
-
-![[Architecture Diagram.png|600]]
-
-Reviewed in [[Meeting Notes 2024-01-10#Decisions]].
-````
-
-## References
-
-- [Obsidian Flavored Markdown](https://help.obsidian.md/obsidian-flavored-markdown)
-- [Internal links](https://help.obsidian.md/links)
-- [Embed files](https://help.obsidian.md/embeds)
-- [Callouts](https://help.obsidian.md/callouts)
-- [Properties](https://help.obsidian.md/properties)

package/stack/skills/obsidian-markdown/references/CALLOUTS.md

@@ -1,58 +0,0 @@
-# Callouts Reference
-
-## Basic Callout
-
-```markdown
-> [!note]
-> This is a note callout.
-
-> [!info] Custom Title
-> This callout has a custom title.
-
-> [!tip] Title Only
-```
-
-## Foldable Callouts
-
-```markdown
-> [!faq]- Collapsed by default
-> This content is hidden until expanded.
-
-> [!faq]+ Expanded by default
-> This content is visible but can be collapsed.
-```
-
-## Nested Callouts
-
-```markdown
-> [!question] Outer callout
-> > [!note] Inner callout
-> > Nested content
-```
-
-## Supported Callout Types
-
-| Type | Aliases | Color / Icon |
-|------|---------|-------------|
-| `note` | - | Blue, pencil |
-| `abstract` | `summary`, `tldr` | Teal, clipboard |
-| `info` | - | Blue, info |
-| `todo` | - | Blue, checkbox |
-| `tip` | `hint`, `important` | Cyan, flame |
-| `success` | `check`, `done` | Green, checkmark |
-| `question` | `help`, `faq` | Yellow, question mark |
-| `warning` | `caution`, `attention` | Orange, warning |
-| `failure` | `fail`, `missing` | Red, X |
-| `danger` | `error` | Red, zap |
-| `bug` | - | Red, bug |
-| `example` | - | Purple, list |
-| `quote` | `cite` | Gray, quote |
-
-## Custom Callouts (CSS)
-
-```css
-.callout[data-callout="custom-type"] {
-  --callout-color: 255, 0, 0;
-  --callout-icon: lucide-alert-circle;
-}
-```

package/stack/skills/obsidian-markdown/references/EMBEDS.md

@@ -1,63 +0,0 @@
-# Embeds Reference
-
-## Embed Notes
-
-```markdown
-![[Note Name]]
-![[Note Name#Heading]]
-![[Note Name#^block-id]]
-```
-
-## Embed Images
-
-```markdown
-![[image.png]]
-![[image.png|640x480]]    Width x Height
-![[image.png|300]]        Width only (maintains aspect ratio)
-```
-
-## External Images
-
-```markdown
-![Alt text](https://example.com/image.png)
-![Alt text|300](https://example.com/image.png)
-```
-
-## Embed Audio
-
-```markdown
-![[audio.mp3]]
-![[audio.ogg]]
-```
-
-## Embed PDF
-
-```markdown
-![[document.pdf]]
-![[document.pdf#page=3]]
-![[document.pdf#height=400]]
-```
-
-## Embed Lists
-
-```markdown
-![[Note#^list-id]]
-```
-
-Where the list has a block ID:
-
-```markdown
-- Item 1
-- Item 2
-- Item 3
-
-^list-id
-```
-
-## Embed Search Results
-
-````markdown
-```query
-tag:#project status:done
-```
-````