opencode-skills-collection 3.0.32 → 3.0.34

package/bundled-skills/schema-markup-generator/SKILL.md

@@ -0,0 +1,319 @@
+---
+name: schema-markup-generator
+description: "Generate and implement JSON-LD structured data for web apps, tool pages, blogs, FAQs, and SaaS sites. Supports WebSite, SoftwareApplication, BlogPosting, FAQPage, HowTo, BreadcrumbList, and Organization schemas."
+category: seo
+risk: safe
+source: self
+source_type: self
+date_added: "2026-05-31"
+author: Whoisabhishekadhikari
+tags: [seo, schema, json-ld, structured-data, rich-results, nextjs, technical-seo]
+tools: [claude, cursor, gemini, claude-code]
+version: 1.0.0
+---
+
+# Schema Markup Generator Skill
+
+Add JSON-LD structured data to pages to unlock rich results, improve CTR, and signal context to Google and AI systems.
+
+---
+
+## When to Use
+
+- Use when adding or auditing JSON-LD schema for websites, SaaS apps, tools, articles, FAQs, breadcrumbs, or organization pages.
+- Use when schema must be implemented in Next.js App Router or validated against Google Rich Results and Schema.org tooling.
+- Use when a page has strong content but lacks structured data for search engines and rich-result eligibility.
+
+---
+
+## How to Add Schema in Next.js App Router
+
+The cleanest approach is a reusable `JsonLd` component:
+
+```jsx
+// components/JsonLd.jsx
+export function JsonLd({ data }) {
+  return (
+    <script
+      type="application/ld+json"
+      dangerouslySetInnerHTML={{ __html: JSON.stringify(data) }}
+    />
+  );
+}
+```
+
+Use it in any page:
+```jsx
+import { JsonLd } from '@/components/JsonLd';
+
+export default function MyPage() {
+  return (
+    <>
+      <JsonLd data={mySchemaObject} />
+      {/* rest of page */}
+    </>
+  );
+}
+```
+
+---
+
+## Schema Types by Page Type
+
+### WebSite + Sitelinks Searchbox (homepage only)
+```js
+{
+  "@context": "https://schema.org",
+  "@type": "WebSite",
+  "name": "100 SEO Tools",
+  "url": "https://www.100seotools.com",
+  "description": "Free online SEO tools for keyword research, technical audits, and more.",
+  "potentialAction": {
+    "@type": "SearchAction",
+    "target": {
+      "@type": "EntryPoint",
+      "urlTemplate": "https://www.100seotools.com/search?q={search_term_string}"
+    },
+    "query-input": "required name=search_term_string"
+  }
+}
+```
+
+---
+
+### SoftwareApplication (tool / SaaS app pages)
+```js
+{
+  "@context": "https://schema.org",
+  "@type": "SoftwareApplication",
+  "name": "Keyword Density Checker",
+  "applicationCategory": "WebApplication",
+  "operatingSystem": "Web",
+  "url": "https://www.100seotools.com/tools/keyword-density-checker",
+  "description": "Free keyword density checker tool. Analyze keyword frequency and optimize your content for SEO.",
+  "offers": {
+    "@type": "Offer",
+    "price": "0",
+    "priceCurrency": "USD"
+  },
+  "featureList": [
+    "Analyze keyword frequency",
+    "Detect over-optimization",
+    "Export results as CSV"
+  ],
+  "provider": {
+    "@type": "Organization",
+    "name": "100 SEO Tools",
+    "url": "https://www.100seotools.com"
+  }
+}
+```
+
+---
+
+### Article / BlogPosting (blog posts)
+```js
+{
+  "@context": "https://schema.org",
+  "@type": "BlogPosting",
+  "headline": "How to Improve Your Core Web Vitals in 2025",
+  "description": "A practical guide to improving LCP, FID, and CLS scores for better rankings.",
+  "url": "https://www.100seotools.com/blog/improve-core-web-vitals",
+  "datePublished": "2025-01-15",
+  "dateModified": "2025-03-20",
+  "author": {
+    "@type": "Person",
+    "name": "Jane Smith",
+    "url": "https://www.100seotools.com/author/jane-smith"
+  },
+  "publisher": {
+    "@type": "Organization",
+    "name": "100 SEO Tools",
+    "logo": {
+      "@type": "ImageObject",
+      "url": "https://www.100seotools.com/logo.png"
+    }
+  },
+  "image": {
+    "@type": "ImageObject",
+    "url": "https://www.100seotools.com/images/blog/core-web-vitals.jpg",
+    "width": 1200,
+    "height": 630
+  },
+  "mainEntityOfPage": {
+    "@type": "WebPage",
+    "@id": "https://www.100seotools.com/blog/improve-core-web-vitals"
+  }
+}
+```
+
+---
+
+### FAQPage (FAQ sections, tool help pages)
+```js
+{
+  "@context": "https://schema.org",
+  "@type": "FAQPage",
+  "mainEntity": [
+    {
+      "@type": "Question",
+      "name": "What is keyword density?",
+      "acceptedAnswer": {
+        "@type": "Answer",
+        "text": "Keyword density is the percentage of times a keyword appears in a piece of content relative to the total word count. A healthy keyword density is typically 1-3%."
+      }
+    },
+    {
+      "@type": "Question",
+      "name": "Is this tool free to use?",
+      "acceptedAnswer": {
+        "@type": "Answer",
+        "text": "Yes, our keyword density checker is completely free with no registration required."
+      }
+    }
+  ]
+}
+```
+
+---
+
+### HowTo (step-by-step tool guides)
+```js
+{
+  "@context": "https://schema.org",
+  "@type": "HowTo",
+  "name": "How to Check Keyword Density",
+  "description": "Step-by-step guide to analyzing keyword density using our free tool.",
+  "totalTime": "PT2M",
+  "step": [
+    {
+      "@type": "HowToStep",
+      "position": 1,
+      "name": "Paste your content",
+      "text": "Copy your article or webpage content and paste it into the text area.",
+      "image": "https://www.100seotools.com/images/how-to/step1.jpg"
+    },
+    {
+      "@type": "HowToStep",
+      "position": 2,
+      "name": "Enter your target keyword",
+      "text": "Type the keyword you want to analyze in the keyword field."
+    },
+    {
+      "@type": "HowToStep",
+      "position": 3,
+      "name": "Click Analyze",
+      "text": "Press the Analyze button to get your keyword density report instantly."
+    }
+  ]
+}
+```
+
+---
+
+### BreadcrumbList (all non-homepage pages)
+```js
+{
+  "@context": "https://schema.org",
+  "@type": "BreadcrumbList",
+  "itemListElement": [
+    {
+      "@type": "ListItem",
+      "position": 1,
+      "name": "Home",
+      "item": "https://www.100seotools.com"
+    },
+    {
+      "@type": "ListItem",
+      "position": 2,
+      "name": "SEO Tools",
+      "item": "https://www.100seotools.com/tools"
+    },
+    {
+      "@type": "ListItem",
+      "position": 3,
+      "name": "Keyword Density Checker",
+      "item": "https://www.100seotools.com/tools/keyword-density-checker"
+    }
+  ]
+}
+```
+
+---
+
+### Organization (about, contact pages)
+```js
+{
+  "@context": "https://schema.org",
+  "@type": "Organization",
+  "name": "100 SEO Tools",
+  "url": "https://www.100seotools.com",
+  "logo": "https://www.100seotools.com/logo.png",
+  "sameAs": [
+    "https://twitter.com/100seotools",
+    "https://www.linkedin.com/company/100seotools"
+  ],
+  "contactPoint": {
+    "@type": "ContactPoint",
+    "contactType": "customer support",
+    "email": "hello@100seotools.com"
+  }
+}
+```
+
+---
+
+## Combining Multiple Schemas on One Page
+
+A tool page can have BreadcrumbList + SoftwareApplication + FAQPage:
+
+```jsx
+export default function ToolPage() {
+  return (
+    <>
+      <JsonLd data={breadcrumbSchema} />
+      <JsonLd data={softwareApplicationSchema} />
+      <JsonLd data={faqSchema} />
+      {/* page content */}
+    </>
+  );
+}
+```
+
+Each schema lives in its own `<script>` tag — do NOT merge them into one object.
+
+---
+
+## Validation
+
+Always validate schema before deploying:
+
+1. **Google Rich Results Test** — https://search.google.com/test/rich-results
+2. **Schema.org Validator** — https://validator.schema.org/
+3. **Google Search Console** → Enhancements → check for warnings after deployment
+
+```bash
+# Quick check: schema appears in HTML
+curl -s https://www.yourdomain.com/tools/keyword-density | grep -A 5 "application/ld+json"
+```
+
+---
+
+## Schema Markup Checklist
+
+- [ ] Homepage has `WebSite` schema
+- [ ] Tool/app pages have `SoftwareApplication` schema
+- [ ] Blog posts have `BlogPosting` / `Article` schema
+- [ ] FAQ sections have `FAQPage` schema
+- [ ] Step-by-step guides have `HowTo` schema
+- [ ] All non-homepage pages have `BreadcrumbList`
+- [ ] About/contact page has `Organization` schema
+- [ ] All URLs in schema are absolute HTTPS
+- [ ] Schema validated with Google Rich Results Test
+- [ ] No schema errors in Google Search Console
+
+## Limitations
+
+- Does not guarantee rich-result eligibility or display; Google and other consumers decide whether to use valid schema.
+- Generated examples must be adapted to the site's real content, legal entity details, ratings, pricing, and availability.
+- Always validate deployed HTML, not only source code, because frameworks and rendering modes can change the final markup.

package/bundled-skills/sendblue/sendblue-api/SKILL.md

@@ -2,13 +2,17 @@
 name: sendblue-api
 description: "Send and receive iMessage, SMS, and RCS from application code via the Sendblue HTTP API — text, media, group messages, send styles, reactions, typing indicators, status callbacks, and inbound webhooks."
 category: api-integration
-risk: safe
+risk: critical
 source: community
 source_type: official
 date_added: "2026-05-22"
 author: AnthonyFirth
 tags: [sendblue, imessage, sms, rcs, messaging, api, webhooks]
 tools: [claude, cursor, gemini]
+plugin:
+  targets:
+    codex: blocked
+    claude: blocked
 ---
 
 # Sendblue API
@@ -167,6 +171,7 @@ Status callback payloads (`outbound`) mirror the send-message response and updat
 ## Security & Safety Notes
 
 - Keep `sb-api-key-id` and `sb-api-secret-key` server-side. They are not safe in browser, mobile, or CI logs.
+- Treat every outbound send, contact/webhook mutation, read receipt, reaction, or typing indicator as state-changing. Preview the recipient, sender line, content, and callback/webhook changes, then wait for explicit user confirmation before sending.
 - Webhook endpoints should be on HTTPS and idempotent — same `message_handle` may arrive more than once.
 - Sensitive data in message content is visible in lock-screen previews on the recipient's device. Don't embed secrets, tokens, or full PII — link to an authenticated dashboard or shortened payload instead.
 - Rotate API keys from the Sendblue dashboard if either value is exposed; the old pair is invalidated on rotation.

package/bundled-skills/sendblue/sendblue-cli/SKILL.md

@@ -2,7 +2,7 @@
 name: sendblue-cli
 description: "Send iMessage and SMS from the shell via the @sendblue/cli npm package — outbound sends, contact management, and account setup with no API client or webhook server required."
 category: api-integration
-risk: safe
+risk: critical
 source: community
 source_repo: sendblue-api/sendblue-cli
 source_type: official
@@ -12,6 +12,10 @@ tags: [sendblue, imessage, sms, cli, messaging, notifications]
 tools: [claude, cursor, gemini]
 license: "MIT"
 license_source: "https://github.com/sendblue-api/sendblue-cli/blob/main/LICENSE"
+plugin:
+  targets:
+    codex: blocked
+    claude: blocked
 ---
 
 # Sendblue CLI
@@ -121,6 +125,7 @@ To text yourself at the end of every agent turn, register a `Stop` hook in `sett
 ## Security & Safety Notes
 
 - Credentials are written to `~/.sendblue/credentials.json` with mode `600`. Treat that file like an API key — do not commit it, do not copy it across machines without the same posture.
+- Treat every outbound send, contact setup, login, or account setup action as state-changing. Preview the recipient, message body, and account/email target, then wait for explicit user confirmation before running it.
 - Run the CLI as the OS user that owns the credentials file. `sudo` writes a separate copy under root's home and silently desyncs.
 - Outbound messages to phone numbers are not free of consequence — wire `sendblue send` into hooks or loops only after gating on duration or success conditions to avoid spamming the recipient.
 - Verification codes arrive by email; treat the address you registered with as a recovery factor for the account.

package/bundled-skills/sendblue/sendblue-notify/SKILL.md

@@ -2,13 +2,17 @@
 name: sendblue-notify
 description: "Text the user's phone when a long-running task, agent turn, or scheduled job finishes — via @sendblue/cli for outbound, optionally wired to a Claude Code Stop hook for automatic fire."
 category: automation
-risk: safe
+risk: critical
 source: community
 source_type: official
 date_added: "2026-05-22"
 author: AnthonyFirth
 tags: [sendblue, imessage, sms, notifications, hooks, claude-code, automation]
 tools: [claude, cursor, gemini]
+plugin:
+  targets:
+    codex: blocked
+    claude: blocked
 ---
 
 # Sendblue Notify
@@ -146,6 +150,7 @@ You can install both: textme on a server for inbound, notify as a local `Stop`-h
 ## Security & Safety Notes
 
 - **Lock-screen previews leak.** Anyone holding the phone can read notification copy. Do not embed secrets, customer data, full error stacks, or auth tokens. Link to a log, dashboard, or PR instead.
+- **Confirm before sending or wiring hooks.** Preview the destination, message template, trigger, and duration gate; wait for explicit user confirmation before running `sendblue send` or editing hook config.
 - **Automated outbound is a footgun.** A misconfigured `Stop` hook can fire dozens of messages a minute. Always gate by duration and prove the threshold in a dry run before committing.
 - **Per-user numbers.** The destination phone number is a personal identifier — keep it in user-local config (env var, gitignored file), not in committed repo files or CI logs.
 - **Free-plan verification is silent.** If the destination contact hasn't texted in once, sends return an API error but the user just sees "no text arrived". Confirm verification before wiring an unattended hook.

package/bundled-skills/sendblue/textme/SKILL.md

@@ -12,6 +12,10 @@ tags: [textme, sendblue, imessage, sms, claude-code, daemon, remote-control, aut
 tools: [claude, cursor, gemini]
 license: "MIT"
 license_source: "https://github.com/njerschow/textme/blob/main/LICENSE"
+plugin:
+  targets:
+    codex: blocked
+    claude: blocked
 ---
 
 # TextMe

package/bundled-skills/social-metadata-hardening/SKILL.md

@@ -0,0 +1,230 @@
+---
+name: social-metadata-hardening
+description: "Fix social sharing previews so URLs render as rich cards on Facebook, LinkedIn, X/Twitter, WhatsApp, Telegram, Slack, and Discord. Covers OG tags, Twitter cards, absolute image URLs, and metadata debugging."
+category: seo
+risk: safe
+source: self
+source_type: self
+date_added: "2026-05-31"
+author: Whoisabhishekadhikari
+tags: [seo, open-graph, twitter-card, social-sharing, og-image, nextjs, metadata]
+tools: [claude, cursor, gemini, claude-code]
+version: 1.0.0
+---
+
+# Social Metadata Hardening Skill
+
+Fix social sharing so every important URL unfurls as a rich card across all platforms.
+
+---
+
+## When to Use
+
+- Use when shared links show missing, stale, cropped, or incorrect previews on social and chat platforms.
+- Use when auditing Open Graph, Twitter/X card, image URL, alt text, or `metadataBase` coverage in a web app.
+- Use before launch when every public page needs predictable rich previews across LinkedIn, X, Facebook, WhatsApp, Slack, Discord, and Telegram.
+
+---
+
+## Why Previews Break
+
+| Problem | Root Cause |
+|---------|-----------|
+| No preview at all | Missing og:title, og:description, or og:image |
+| Broken image | Relative URL (must be absolute) |
+| Wrong image size | Image not 1200×630px (OG standard) |
+| Plain text card | Twitter card type missing or set to `summary` |
+| Stale preview | Platform caching old metadata |
+| Metadata missing on crawl | Tags added by client-side JS (crawlers don't run JS) |
+
+---
+
+## The Gold Standard Metadata Block
+
+Every shareable page needs ALL of these in static HTML:
+
+```js
+// Next.js App Router — lib/socialMetadata.js
+export function buildSocialMetadata({
+  title,
+  description,
+  path,          // '/blog/my-post'
+  image,         // '/images/og/my-post.jpg' or full URL
+  imageAlt,
+  imageWidth = 1200,
+  imageHeight = 630,
+}) {
+  const baseUrl = process.env.NEXT_PUBLIC_BASE_URL || 'https://www.yourdomain.com';
+  
+  // Always produce an absolute URL
+  const imageUrl = image?.startsWith('http') ? image : `${baseUrl}${image}`;
+  const pageUrl  = `${baseUrl}${path}`;
+  
+  // Detect MIME type from extension
+  const ext = imageUrl.split('.').pop().toLowerCase();
+  const mimeMap = { jpg: 'image/jpeg', jpeg: 'image/jpeg', png: 'image/png', webp: 'image/webp' };
+  const imageType = mimeMap[ext] || 'image/jpeg';
+
+  return {
+    title,
+    description,
+    alternates: { canonical: pageUrl },
+    openGraph: {
+      title,
+      description,
+      url: pageUrl,
+      type: 'website',  // use 'article' for blog posts
+      images: [{
+        url: imageUrl,
+        secureUrl: imageUrl,   // explicit HTTPS version
+        width: imageWidth,
+        height: imageHeight,
+        alt: imageAlt || title,
+        type: imageType,
+      }],
+    },
+    twitter: {
+      card: 'summary_large_image',  // NOT 'summary' — that shows a tiny image
+      title,
+      description,
+      images: [imageUrl],
+    },
+  };
+}
+```
+
+---
+
+## Applying the Helper
+
+### Static page
+```js
+// app/about/page.js
+import { buildSocialMetadata } from '@/lib/socialMetadata';
+
+export const metadata = buildSocialMetadata({
+  title: 'About Us | My Site',
+  description: 'Learn about our team and mission.',
+  path: '/about',
+  image: '/images/og/about.jpg',
+  imageAlt: 'The My Site team',
+});
+```
+
+### Dynamic page (blog post, tool page)
+```js
+// app/blog/[slug]/page.js
+import { buildSocialMetadata } from '@/lib/socialMetadata';
+
+export async function generateMetadata({ params }) {
+  const post = await getPost(params.slug);
+  return buildSocialMetadata({
+    title: `${post.title} | My Blog`,
+    description: post.excerpt,
+    path: `/blog/${params.slug}`,
+    image: post.ogImage || '/images/og/default.jpg',
+    imageAlt: post.title,
+  });
+}
+```
+
+### Homepage (app/layout.js or app/page.js)
+```js
+export const metadata = {
+  metadataBase: new URL('https://www.yourdomain.com'), // REQUIRED for absolute URLs
+  ...buildSocialMetadata({
+    title: 'My Site — Tagline Here',
+    description: 'Site-wide description.',
+    path: '/',
+    image: '/images/og/home.jpg',
+  }),
+};
+```
+
+> ⚠️ **`metadataBase` is critical.** Without it, Next.js generates relative OG image URLs that every platform rejects.
+
+---
+
+## OG Image Checklist
+
+Good OG images:
+- **1200 × 630px** (2:1 ratio — works on all platforms)
+- **Under 8MB** (Facebook limit)
+- Served over **HTTPS**
+- File name has **no spaces** (use hyphens)
+- Format: **JPEG or PNG** (WebP works on most but not all crawlers)
+- **Accessible via GET** with no authentication
+
+```bash
+# Verify your OG image is reachable and correct size
+curl -sI https://www.yourdomain.com/images/og/home.jpg | grep -i "content-type\|content-length\|status"
+```
+
+---
+
+## Platform-Specific Notes
+
+### Facebook / Meta
+- Caches aggressively — use the [Sharing Debugger](https://developers.facebook.com/tools/debug/) to force recrawl
+- Minimum image: 200×200px (but use 1200×630 for quality)
+- Needs: `og:title`, `og:description`, `og:image`, `og:url`
+
+### X / Twitter
+- Use `twitter:card = summary_large_image` for full-width images
+- `twitter:image` must be an absolute URL
+- Use the [Card Validator](https://cards-dev.twitter.com/validator) to test
+
+### LinkedIn
+- Caches hard — use [Post Inspector](https://www.linkedin.com/post-inspector/) to refresh
+- Respects `og:` tags; ignores `twitter:` tags
+- Image must be ≥1.91:1 aspect ratio
+
+### WhatsApp / Telegram
+- Read OG tags on first share; cache can last hours
+- Re-share after a few hours for the cache to clear naturally
+
+### Slack / Discord
+- Both use OG tags; both cache
+- Discord also supports `og:type = article` for richer embeds
+
+---
+
+## Debugging Social Previews
+
+### 1. Check raw HTML for tags
+```bash
+curl -s https://www.yourdomain.com/blog/my-post | grep -i "og:\|twitter:"
+```
+If tags don't appear → they're being added by JavaScript (not crawlable). Fix: move to `export const metadata` or `generateMetadata`.
+
+### 2. Validate with platform tools
+| Platform | Tool |
+|----------|------|
+| Facebook | https://developers.facebook.com/tools/debug/ |
+| LinkedIn | https://www.linkedin.com/post-inspector/ |
+| Twitter/X | https://cards-dev.twitter.com/validator |
+| General | https://metatags.io |
+
+### 3. Force cache refresh
+After deploying fixes, paste the URL into each platform's debugger and click "Fetch new scrape information" (or equivalent).
+
+---
+
+## Social Metadata Checklist
+
+- [ ] `metadataBase` set in root layout
+- [ ] All shareable pages use shared `buildSocialMetadata` helper
+- [ ] OG image URLs are absolute (start with `https://`)
+- [ ] `secureUrl` set equal to `url` in OG image block
+- [ ] Image is 1200×630px, under 8MB, HTTPS
+- [ ] `twitter:card` is `summary_large_image` (not `summary`)
+- [ ] Image alt text present
+- [ ] Tags visible in raw HTML (not JavaScript-rendered)
+- [ ] All platform debuggers show correct preview
+- [ ] Cache refreshed on all platforms after deployment
+
+## Limitations
+
+- Cannot force immediate cache refresh on every social platform; some previews may remain stale after a correct fix.
+- Requires deployed, publicly reachable URLs for reliable validation with platform debuggers.
+- Does not replace brand, accessibility, or legal review of image text, alt text, and preview copy.

package/bundled-skills/socialclaw/SKILL.md

@@ -2,7 +2,7 @@
 name: socialclaw
 description: "Agent-first social media publishing skill — schedule and publish posts across 13 platforms (X, LinkedIn, Instagram, Facebook Pages, TikTok, Discord, Telegram, YouTube, Reddit, WordPress, Pinterest) via a single workspace API key."
 category: marketing
-risk: safe
+risk: critical
 source: community
 source_repo: ndesv21/socialclaw
 source_type: community
@@ -12,6 +12,10 @@ tags: [social-media, publishing, scheduling, marketing, twitter, linkedin, insta
 tools: [claude]
 license: "MIT"
 license_source: "https://github.com/ndesv21/socialclaw/blob/main/LICENSE"
+plugin:
+  targets:
+    codex: blocked
+    claude: blocked
 ---
 
 # SocialClaw — Social Media Publisher
@@ -103,5 +107,6 @@ Website: [getsocialclaw.com](https://getsocialclaw.com)
 ## Limitations
 
 - Requires a valid SocialClaw workspace API key; do not attempt publishing without explicit user-provided credentials.
+- Treat every publish, schedule, delete, or account-changing action as state-changing: show the target platforms, content, media, and timing, then wait for explicit user confirmation before calling the service.
 - Platform availability, rate limits, analytics fields, and scheduling behavior depend on the upstream SocialClaw service.
 - This skill describes the publishing workflow; it does not replace platform-specific compliance, brand review, or legal approval before posting.

package/bundled-skills/uv-package-manager/resources/implementation-playbook.md

@@ -51,9 +51,11 @@ Comprehensive guide to using uv, an extremely fast Python package installer and
 
 ```bash
 # macOS/Linux
-curl -LsSf https://astral.sh/uv/install.sh -o /tmp/uv-install.sh
-sed -n '1,160p' /tmp/uv-install.sh
-sh /tmp/uv-install.sh
+tmpdir="$(mktemp -d)"
+trap 'rm -rf "$tmpdir"' EXIT
+curl -LsSf https://astral.sh/uv/install.sh -o "$tmpdir/uv-install.sh"
+sed -n '1,160p' "$tmpdir/uv-install.sh"
+sh "$tmpdir/uv-install.sh"
 
 # Windows (PowerShell)
 powershell -NoProfile -Command "Invoke-WebRequest https://astral.sh/uv/install.ps1 -OutFile $env:TEMP\\uv-install.ps1; Get-Content $env:TEMP\\uv-install.ps1 -TotalCount 120; powershell -ExecutionPolicy Bypass -File $env:TEMP\\uv-install.ps1"