@web42/w42 0.1.4 → 0.1.8

package/skills/web42-publish-prep/references/marketplace-config.md

@@ -1,99 +0,0 @@
-# Marketplace Configuration Reference
-
-The file `.web42/marketplace.json` controls how your agent appears and is sold on the Web42 marketplace. It is created automatically by `web42 init` with sensible defaults.
-
-## File Location
-
-```
-.web42/marketplace.json
-```
-
-## Fields
-
-### `price_cents` (number)
-
-The price in cents. `0` means free.
-
-- **Default:** `0`
-- **Examples:** `0` (free), `500` ($5.00), `2999` ($29.99), `10000` ($100.00)
-- **Guidance:**
-  - Free agents get more installs but less revenue. Consider free for simple utilities, paid for specialized workflows.
-  - Look at comparable agents on the marketplace for pricing cues.
-  - $5–$15 is a sweet spot for productivity agents. $20–$50 for specialized professional tools.
-  - You can always start free and add pricing later.
-
-### `currency` (string)
-
-ISO 4217 currency code.
-
-- **Default:** `"usd"`
-- **Values:** Currently only `"usd"` is supported.
-
-### `license` (string | null)
-
-The license under which the agent is distributed. `null` means no license specified.
-
-- **Default:** `null`
-- **Supported values:**
-
-| License | Summary | Best For |
-|---------|---------|----------|
-| `"MIT"` | Permissive. Buyers can do almost anything. | Open tools, community agents |
-| `"Apache-2.0"` | Permissive + patent grant. | Enterprise-friendly tools |
-| `"GPL-3.0"` | Copyleft. Derivatives must also be GPL. | Agents you want to stay open |
-| `"BSD-3-Clause"` | Permissive, similar to MIT. | Academic or research agents |
-| `"Proprietary"` | All rights reserved. No redistribution. | Commercial/paid agents |
-| `"Custom"` | Custom terms defined elsewhere. | Unique licensing needs |
-
-- **Guidance:**
-  - For **free agents** intended as community contributions: `MIT` or `Apache-2.0`.
-  - For **paid agents**: `Proprietary` is the standard choice — buyers get usage rights but cannot redistribute.
-  - If unsure, `MIT` for free and `Proprietary` for paid is a safe default.
-
-### `tags` (string array)
-
-Searchable labels for marketplace discoverability. These are the canonical tags shown on the marketplace listing.
-
-- **Default:** `[]`
-- **Constraints:** Each tag should be lowercase, hyphenated for multi-word.
-- **Good:** `["crm", "slack-integration", "weekly-reports", "productivity"]`
-- **Bad:** `["ai", "agent", "good", "cool"]` (too generic)
-- **Guidance:**
-  - Use 3–6 tags.
-  - Mix **category terms** ("finance", "devops", "support") with **capability terms** ("pdf-generation", "slack-integration", "email-monitoring").
-  - Think about what a buyer would search for to find your agent.
-  - Tags also appear in the manifest — the marketplace.json tags are the canonical source that gets synced to the remote.
-
-## Visibility (Dashboard Only)
-
-Agent visibility is **not** controlled through local files. It is managed exclusively through the Web42 dashboard at `web42.ai`.
-
-The visibility lifecycle:
-
-1. **`private`** (default) — Only you can see it. Use this while developing and preparing.
-2. **`unlisted`** — Accessible via direct link but not in search/browse. Good for beta testers or early feedback.
-3. **`public`** — Visible to everyone on the marketplace. Set this when you're ready to launch.
-
-Remind the user to visit the dashboard to toggle visibility when the agent is ready.
-
-## Example File
-
-```json
-{
-  "price_cents": 999,
-  "currency": "usd",
-  "license": "Proprietary",
-  "tags": [
-    "crm",
-    "slack-integration",
-    "weekly-reports",
-    "productivity"
-  ]
-}
-```
-
-## Sync Behavior
-
-When you run `web42 push`, the contents of `.web42/marketplace.json` are included in the sync snapshot and written to the remote database. When you run `web42 pull`, remote marketplace settings (except visibility) are written back to this file.
-
-Changes made on the dashboard (e.g., editing tags or price via the web UI) will be reflected locally on the next `web42 pull`.

package/skills/web42-publish-prep/references/resources-guide.md

@@ -1,136 +0,0 @@
-# Resources Guide
-
-Resources are the visual media and documents that accompany your agent's marketplace listing: screenshots, demo videos, architecture diagrams, PDF guides, etc. They make listings dramatically more compelling.
-
-## File Locations
-
-```
-.web42/resources.json        # Metadata describing each resource
-.web42/resources/             # The actual resource files
-  screenshot-dashboard.png
-  demo-recording.mp4
-  setup-guide.pdf
-```
-
-## `resources.json` Schema
-
-The file is a JSON array of `ResourceMeta` objects:
-
-```json
-[
-  {
-    "file": "screenshot-dashboard.png",
-    "title": "Dashboard Overview",
-    "description": "The main dashboard showing weekly report generation",
-    "type": "image",
-    "sort_order": 0
-  },
-  {
-    "file": "demo-recording.mp4",
-    "title": "3-Minute Demo",
-    "description": "Watch the agent draft a report from CRM data in real time",
-    "type": "video",
-    "sort_order": 1
-  }
-]
-```
-
-### Fields
-
-| Field | Type | Required | Description |
-|-------|------|----------|-------------|
-| `file` | string | Yes | Filename in `.web42/resources/` |
-| `title` | string | Yes | Display title on the marketplace listing |
-| `description` | string | No | Optional caption or context |
-| `type` | `"image"` \| `"video"` \| `"document"` | Yes | Determines how the marketplace renders it |
-| `sort_order` | number | Yes | Display order (0 = first) |
-
-## Resource Types
-
-### Images
-
-Screenshots, diagrams, architecture overviews, result samples.
-
-- **Recommended:** 1200x800 or 1600x900 (16:9 landscape)
-- **Formats:** PNG, JPEG, WebP
-- **Max size:** 5 MB per file
-- **Tips:**
-  - Lead with your best screenshot — it appears first in the gallery.
-  - Show the agent *in action*, not just a static interface.
-  - Annotate screenshots with callouts if key features are not obvious.
-  - Dark-mode and light-mode variants both work well.
-
-### Videos
-
-Demo recordings, walkthroughs, setup tutorials.
-
-- **Recommended:** 1–3 minutes for demos, under 60 seconds for teasers
-- **Formats:** MP4, WebM
-- **Max size:** 50 MB per file (for local storage; consider hosting large videos externally)
-- **Tips:**
-  - Start with the outcome, not the setup. Show the result in the first 10 seconds.
-  - Screen recordings with voiceover convert better than silent ones.
-  - For large video files, consider hosting on YouTube/Loom and linking via `demoVideoUrl` in the manifest instead.
-
-### Documents
-
-PDF guides, setup instructions, architecture docs.
-
-- **Formats:** PDF
-- **Max size:** 10 MB per file
-- **Tips:**
-  - Use for detailed setup guides that are too long for the README.
-  - A 1-page "quick start" PDF is a nice touch for complex agents.
-
-## How Resources Appear on the Marketplace
-
-Resources are displayed on the agent's detail page:
-
-- **Images** show as a scrollable gallery below the agent header.
-- **Videos** embed with a play button.
-- **Documents** appear as downloadable links.
-
-The `sort_order` controls the display sequence across all types.
-
-## Sync Behavior
-
-When you run `web42 push`, the CLI:
-
-1. Reads `.web42/resources.json` for metadata.
-2. Uploads each file from `.web42/resources/` to the server.
-3. Creates the corresponding `agent_resources` rows in the database.
-
-When you run `web42 pull`, the CLI writes `.web42/resources.json` with metadata from the remote. Resource files themselves are not downloaded back (they are referenced by URL in the snapshot).
-
-## Example Workflow
-
-1. Take screenshots of your agent in action.
-2. Save them to `.web42/resources/`.
-3. Create or update `.web42/resources.json` with metadata for each file.
-4. Run `web42 push` — the resources upload alongside everything else.
-
-```json
-[
-  {
-    "file": "slack-report.png",
-    "title": "Weekly Report in Slack",
-    "description": "Automated report posted to #team-updates every Monday",
-    "type": "image",
-    "sort_order": 0
-  },
-  {
-    "file": "crm-dashboard.png",
-    "title": "CRM Data View",
-    "description": "The agent reads from your CRM and extracts key metrics",
-    "type": "image",
-    "sort_order": 1
-  },
-  {
-    "file": "setup-guide.pdf",
-    "title": "Setup Guide",
-    "description": "Step-by-step guide for connecting your CRM and Slack",
-    "type": "document",
-    "sort_order": 2
-  }
-]
-```

package/skills/web42-publish-prep/references/web42-folder.md

@@ -1,120 +0,0 @@
-# The `.web42/` Folder
-
-The `.web42/` directory in your agent workspace is the metadata and sync hub for the Web42 marketplace. It is created automatically by `web42 init`.
-
-## Structure
-
-```
-.web42/
-├── marketplace.json     # Pricing, license, tags
-├── resources.json       # Metadata for resource files
-├── sync.json            # Sync state (auto-managed, do not edit)
-├── avatar.png           # Agent profile image (optional)
-├── resources/           # Screenshots, videos, documents
-│   ├── screenshot-1.png
-│   └── demo.mp4
-└── dist/                # Pack output (auto-generated by web42 pack)
-    ├── AGENTS.md
-    ├── IDENTITY.md
-    ├── manifest.json
-    └── ...
-```
-
-## Files You Edit
-
-### `marketplace.json`
-
-Controls pricing, licensing, and discoverability on the marketplace.
-
-- Created by `web42 init` with defaults.
-- Edit manually or with agent assistance.
-- Synced to/from the remote on push/pull.
-- See `references/marketplace-config.md` for the full field reference.
-
-### `resources.json`
-
-Describes the resource files (screenshots, videos, documents) in the `resources/` subdirectory.
-
-- JSON array of `ResourceMeta` objects.
-- Each entry maps a file in `resources/` to a title, description, type, and display order.
-- See `references/resources-guide.md` for the schema and guidance.
-
-### `avatar.{png,jpg,jpeg,webp,svg}`
-
-The agent's profile image, shown on the marketplace listing and search results.
-
-- Only one avatar file should exist (the CLI picks the first match by extension priority: png, jpg, jpeg, webp, svg).
-- Recommended: 400x400 or larger, square aspect ratio.
-- Uploaded to the server on `web42 push`.
-
-### `resources/`
-
-Directory containing the actual resource files referenced by `resources.json`.
-
-- Drop images, videos, or PDFs here.
-- Filenames must match the `file` field in `resources.json`.
-
-## Files You Should NOT Edit
-
-### `sync.json`
-
-Tracks the sync state between your local workspace and the remote database.
-
-```json
-{
-  "agent_id": "0c4cc49e-...",
-  "last_remote_hash": "7b1d3ecf...",
-  "last_local_hash": "d9a10b8a...",
-  "synced_at": "2026-03-17T03:54:46.124Z"
-}
-```
-
-- **Auto-managed** by `web42 push`, `web42 pull`, and `web42 sync`.
-- Editing this file manually will break change detection.
-- Safe to delete if you want to force a full re-sync (next push/pull will recreate it).
-
-### `dist/`
-
-The pack output directory, generated by `web42 pack` or automatically during `web42 push`.
-
-- Contains the processed, distributable version of your agent files.
-- **Auto-generated** — do not edit files here directly.
-- Excluded from the pack itself (no recursion).
-
-## Git Integration
-
-Add `.web42/sync.json` and `.web42/dist/` to `.gitignore` since they are auto-generated:
-
-```gitignore
-.web42/sync.json
-.web42/dist/
-```
-
-Keep these in version control:
-
-- `.web42/marketplace.json`
-- `.web42/resources.json`
-- `.web42/avatar.*`
-- `.web42/resources/`
-
-## `.web42ignore` (Workspace Root)
-
-Not inside `.web42/` — lives at the workspace root alongside `manifest.json`.
-
-- Created by `web42 init` with sensible defaults (IDE dirs, env files, test folders, drafts).
-- Glob patterns, one per line. Lines starting with `#` are comments.
-- Controls which files are excluded when running `web42 pack` or `web42 push`.
-- Use `web42 pack --dry-run` to verify what gets included/excluded.
-- See `references/file-hygiene.md` for full details.
-
-Keep `.web42ignore` in version control so the ignore rules travel with the project.
-
-## Sync Lifecycle
-
-```
-web42 init     → Creates .web42/, marketplace.json, resources.json, .web42ignore
-web42 pack     → Generates .web42/dist/ from workspace files (respects .web42ignore)
-web42 push     → Sends snapshot (manifest + README + marketplace + files + avatar + resources) to remote
-web42 pull     → Fetches remote snapshot, writes to local files
-web42 sync     → Shows local vs remote hash comparison without changing anything
-```