@drunkcoding/agents-and-skills 0.0.44 → 0.0.46

package/plugins/team-share/skills/claude-config/SKILL.md

@@ -1,143 +0,0 @@
----
-name: claude-config
-description: Write a shareable .claude/settings.json from the maintainer's enabled plugins and marketplaces, scaffold CLAUDE.md when missing, inject the Understand-Anything code-research section, and stage the result. Idempotent — safe to re-run.
-allowed-tools: Bash, Read, Write, Edit
----
-
-# claude-config
-
-Set up repo-level Claude Code configuration for teammates.
-
-## Preconditions (stop on any failure)
-
-```bash
-git rev-parse --is-inside-work-tree || { echo "ERROR: not a git repo"; exit 1; }
-command -v jq || echo "MISSING: jq — install it (brew install jq / apt install jq / choco install jq) before continuing"
-```
-
-If not a git repo or `jq` is missing → report and STOP. Do not partially apply.
-
-Check current branch and warn if on a protected branch:
-
-```bash
-BRANCH=$(git rev-parse --abbrev-ref HEAD)
-case "$BRANCH" in
-  main|master|develop|dev)
-    echo "⚠️  You are on branch '$BRANCH'. Consider switching to a feature branch before continuing."
-    ;;
-esac
-```
-
-## Step 1 — Merge plugin + marketplace settings
-
-Copy only `enabledPlugins` and `extraKnownMarketplaces` from the maintainer's user settings into the repo settings. Do NOT copy `hooks`, `permissions`, `env`, or any key with absolute paths.
-
-```bash
-USER_SETTINGS="$HOME/.claude/settings.json"
-REPO_SETTINGS=".claude/settings.json"
-
-mkdir -p .claude
-[ -f "$REPO_SETTINGS" ] || echo '{}' > "$REPO_SETTINGS"
-
-jq -s '
-  .[0] as $repo | .[1] as $user
-  | $repo
-  + { enabledPlugins:         (($repo.enabledPlugins         // {}) + ($user.enabledPlugins         // {})) }
-  + { extraKnownMarketplaces: (($repo.extraKnownMarketplaces // {}) + ($user.extraKnownMarketplaces // {})) }
-' "$REPO_SETTINGS" "$USER_SETTINGS" > "$REPO_SETTINGS.tmp" && mv "$REPO_SETTINGS.tmp" "$REPO_SETTINGS"
-
-jq '{enabledPlugins, extraKnownMarketplaces}' "$REPO_SETTINGS"
-```
-
-Inspect the result: flag any marketplace URL that looks private (contains org names, auth tokens, or is not a well-known public registry).
-
-## Step 2 — Scaffold CLAUDE.md if missing
-
-```bash
-if [ -f CLAUDE.md ]; then
-  echo "✅ CLAUDE.md already exists — skipping."
-else
-  echo "📝 CLAUDE.md not found — installing claude-code-setup plugin to scaffold it…"
-  claude plugin install claude-code-setup@claude-plugins-official
-  if [ -f CLAUDE.md ]; then
-    echo "✅ CLAUDE.md created by claude-code-setup."
-  else
-    echo "⚠️  claude-code-setup did not produce CLAUDE.md — create it manually or commit a template first."
-  fi
-fi
-```
-
-## Step 3 — Inject Understand-Anything section into CLAUDE.md
-
-Append only when the section marker is absent (idempotent guard):
-
-```bash
-if grep -qF '## Code research with Understand-Anything' CLAUDE.md 2>/dev/null; then
-  echo "✅ Understand-Anything section already in CLAUDE.md — skipping."
-else
-  cat >> CLAUDE.md << 'UASECTION'
-
-## Code research with Understand-Anything
-
-This project uses the [Understand-Anything](https://github.com/Egonex-AI/Understand-Anything) plugin to maintain an interactive knowledge graph of the codebase. **Always prefer these commands over raw file-by-file exploration when doing code research:**
-
-| Goal | Command |
-|------|---------|
-| Explore the full codebase graph | `/understand` |
-| Ask a free-form question about the code | `/understand-chat <question>` |
-| Deep-dive into a specific file or function | `/understand-explain <path/symbol>` |
-| See impact of your current changes before committing | `/understand-diff` |
-| Open the interactive visual dashboard | `/understand-dashboard` |
-| Extract business-domain knowledge (domains, flows, steps) | `/understand-domain` |
-| Generate an onboarding guide for new teammates | `/understand-onboard` |
-| Generate or refresh wiki knowledge under `docs/wiki` | `/understand-knowledge docs/wiki` |
-
-The knowledge graph lives in `.understand-anything/knowledge-graph.json` and is kept up-to-date automatically on every commit (auto-update is enabled). Re-run `/understand` after large refactors to force a rebuild, and `/understand-knowledge docs/wiki` to refresh the wiki.
-UASECTION
-  echo "✅ Understand-Anything section appended to CLAUDE.md."
-fi
-```
-
-Mirror to AGENTS.md / MIRRORS.md if they exist:
-
-```bash
-for f in AGENTS.md MIRRORS.md; do
-  if [ -f "$f" ] && ! grep -qF '## Code research with Understand-Anything' "$f" 2>/dev/null; then
-    cat >> "$f" << 'UASECTION'
-
-## Code research with Understand-Anything
-
-This project uses the [Understand-Anything](https://github.com/Egonex-AI/Understand-Anything) plugin to maintain an interactive knowledge graph of the codebase. **Always prefer these commands over raw file-by-file exploration when doing code research:**
-
-| Goal | Command |
-|------|---------|
-| Explore the full codebase graph | `/understand` |
-| Ask a free-form question about the code | `/understand-chat <question>` |
-| Deep-dive into a specific file or function | `/understand-explain <path/symbol>` |
-| See impact of your current changes before committing | `/understand-diff` |
-| Open the interactive visual dashboard | `/understand-dashboard` |
-| Extract business-domain knowledge (domains, flows, steps) | `/understand-domain` |
-| Generate an onboarding guide for new teammates | `/understand-onboard` |
-| Generate or refresh wiki knowledge under `docs/wiki` | `/understand-knowledge docs/wiki` |
-
-The knowledge graph lives in `.understand-anything/knowledge-graph.json` and is kept up-to-date automatically on every commit (auto-update is enabled). Re-run `/understand` after large refactors to force a rebuild, and `/understand-knowledge docs/wiki` to refresh the wiki.
-UASECTION
-    echo "✅ Section also appended to $f."
-  fi
-done
-```
-
-## Step 4 — Stage
-
-```bash
-git add .claude/settings.json CLAUDE.md
-for f in AGENTS.md MIRRORS.md; do [ -f "$f" ] && git add "$f"; done
-git status
-```
-
-## Done — report
-
-- Which plugins/marketplaces were written to `.claude/settings.json` (flag any private ones).
-- `CLAUDE.md` status: already existed vs created; Understand-Anything section added vs already present.
-- `AGENTS.md` / `MIRRORS.md` status (if applicable).
-- Files staged. Remind: **review then commit yourself.**

package/plugins/team-share/skills/codegraph-setup/SKILL.md

@@ -1,81 +0,0 @@
----
-name: codegraph-setup
-description: Install the CodeGraph CLI, wire it to the local project via MCP (codegraph install --target=auto --location=local), and initialise the current project (codegraph init). Works on macOS, Linux, and Windows (Git Bash / PowerShell). Idempotent — skips install if codegraph is already in PATH.
-allowed-tools: Bash
----
-
-# codegraph-setup
-
-Install CodeGraph and initialise it for this project.
-
-## Precondition
-
-Must be inside a git repo:
-
-```bash
-git rev-parse --is-inside-work-tree || { echo "ERROR: not a git repo — run this from your project root"; exit 1; }
-```
-
-## Step 1 — Install CLI if not present (OS-aware, idempotent)
-
-Run this as a single bash block so variables persist:
-
-```bash
-if command -v codegraph >/dev/null 2>&1; then
-  echo "✅ codegraph already installed: $(codegraph --version 2>/dev/null || echo 'version unknown')"
-  echo "Skipping install — proceeding to wire and init."
-else
-  if command -v uname >/dev/null 2>&1; then
-    _OS=$(uname -s)
-  else
-    _OS="Windows"
-  fi
-
-  case "$_OS" in
-    Darwin|Linux)
-      curl -fsSL https://raw.githubusercontent.com/colbymchenry/codegraph/main/install.sh | sh
-      ;;
-    *)
-      _PS=$(command -v pwsh 2>/dev/null || command -v powershell 2>/dev/null)
-      if [ -n "$_PS" ]; then
-        "$_PS" -Command "irm https://raw.githubusercontent.com/colbymchenry/codegraph/main/install.ps1 | iex"
-      else
-        echo "ERROR: cannot detect OS or find PowerShell."
-        echo "Install manually: https://github.com/colbymchenry/codegraph#installation"
-        exit 1
-      fi
-      ;;
-  esac
-
-  command -v codegraph >/dev/null 2>&1 || { echo "ERROR: codegraph install failed — not found in PATH after install"; exit 1; }
-  echo "✅ codegraph installed: $(codegraph --version 2>/dev/null || echo 'version unknown')"
-fi
-```
-
-Note: on Windows with Git Bash, `uname -s` returns `MINGW64_NT-*` or similar, which falls through to the `*)` case and attempts PowerShell. This is correct behaviour.
-
-## Step 3 — Wire to your AI tool
-
-Register the CodeGraph MCP server for this project (auto-detects AI tool; config written to project-local settings):
-
-```bash
-codegraph install --target=auto --location=local
-```
-
-This makes CodeGraph's context tools available inside your AI tool's sessions.
-
-## Step 4 — Initialise the project
-
-Build the code knowledge graph for this repo:
-
-```bash
-codegraph init
-```
-
-This creates a local SQLite index of symbols, dependencies, and cross-file relationships.
-
-## Done — report
-
-- Install: new install vs already present (version).
-- Wire: `codegraph install` output.
-- Init: `codegraph init` output, any errors.

package/plugins/team-share/skills/understand-setup/SKILL.md

@@ -1,115 +0,0 @@
----
-name: understand-setup
-description: Install the Understand-Anything plugin, build the knowledge graph with auto-update enabled, generate docs/wiki, git-lfs track the graph, and stage all artefacts. Idempotent — safe to re-run.
-argument-hint: "[--force] [--language <lang>] (passed through to /understand)"
-allowed-tools: Bash, Read, Write, Edit, Skill
----
-
-# understand-setup
-
-Install Understand-Anything and build the knowledge graph for this repo.
-
-## Preconditions (stop on any failure)
-
-```bash
-git rev-parse --is-inside-work-tree || { echo "ERROR: not a git repo"; exit 1; }
-command -v git-lfs || echo "MISSING: git-lfs — install it (brew install git-lfs / apt install git-lfs) before continuing"
-command -v jq      || echo "MISSING: jq — install it (brew install jq / apt install jq / choco install jq) before continuing"
-```
-
-If not a git repo, or `git-lfs`/`jq` are missing → report and STOP. Do not partially apply.
-
-Check current branch and warn if on a protected branch:
-
-```bash
-BRANCH=$(git rev-parse --abbrev-ref HEAD)
-case "$BRANCH" in
-  main|master|develop|dev)
-    echo "⚠️  You are on branch '$BRANCH'. Consider switching to a feature branch first."
-    ;;
-esac
-```
-
-## Step 1 — Install the plugin
-
-Install via the Claude Code plugin system (idempotent):
-
-```
-/plugin marketplace add Egonex-AI/Understand-Anything
-/plugin install understand-anything
-```
-
-After install, confirm `understand-anything@understand-anything` appears in `.claude/settings.json`:
-
-```bash
-jq '.enabledPlugins["understand-anything@understand-anything"]' .claude/settings.json 2>/dev/null || echo "⚠️  understand-anything not found in .claude/settings.json — teammates may need to install manually."
-```
-
-## Step 2 — Build / refresh the knowledge graph
-
-Run the skill **in the main thread** (it dispatches its own analyzer subagents — do not wrap it in a subagent):
-
-```
-/understand --auto-update $ARGUMENTS
-```
-
-- `--auto-update` writes `{"autoUpdate": true}` to `.understand-anything/config.json`.
-- If a graph already exists, `/understand` runs incrementally. Pass `--force` (via `$ARGUMENTS`) to rebuild from scratch.
-
-After it finishes, confirm these files exist:
-
-```bash
-test -f .understand-anything/knowledge-graph.json && echo "✅ knowledge-graph.json" || echo "❌ knowledge-graph.json missing"
-test -f .understand-anything/meta.json            && echo "✅ meta.json"            || echo "❌ meta.json missing"
-jq '.autoUpdate' .understand-anything/config.json 2>/dev/null | grep -q true && echo "✅ autoUpdate: true" || echo "❌ autoUpdate not set"
-```
-
-## Step 3 — Initialize the docs wiki
-
-```bash
-mkdir -p docs/wiki
-```
-
-Run wiki generation in the main thread:
-
-```
-/understand-knowledge docs/wiki
-```
-
-After it finishes, confirm `docs/wiki/` contains generated files:
-
-```bash
-ls docs/wiki/ | head -5 || echo "❌ docs/wiki is empty or missing"
-```
-
-## Step 4 — Ignore scratch outputs, git-lfs track, and stage
-
-Append scratch paths to .gitignore (idempotent):
-
-```bash
-for p in ".understand-anything/intermediate/" ".understand-anything/tmp/" ".understand-anything/diff-overlay.json"; do
-  grep -qxF "$p" .gitignore 2>/dev/null || echo "$p" >> .gitignore
-done
-```
-
-Track large graph files with git-lfs (harmless for small graphs):
-
-```bash
-git lfs install
-git lfs track ".understand-anything/*.json"
-```
-
-Stage all artefacts:
-
-```bash
-git add .gitattributes .gitignore .understand-anything/ docs/wiki/
-git status
-git lfs ls-files
-```
-
-## Done — report
-
-- Graph status: created vs incrementally updated; `autoUpdate` on/off.
-- Wiki status: `docs/wiki/` created vs already existed; generation successful vs failed.
-- Staged files; LFS-tracked files confirmed.
-- Remind: **review then commit yourself.**

package/plugins/tech-graph/.claude-plugin/plugin.json

@@ -1,17 +0,0 @@
-{
-  "name": "tech-graph",
-  "version": "0.0.44",
-  "description": "Step-by-step wizard for generating technical diagrams as SVG+PNG.",
-  "author": {
-    "name": "steven"
-  },
-  "keywords": [
-    "diagram",
-    "svg",
-    "architecture",
-    "uml",
-    "flowchart",
-    "sequence",
-    "er"
-  ]
-}

package/plugins/tech-graph/README.md

@@ -1,66 +0,0 @@
-# tech-graph
-
-Step-by-step wizard for generating technical diagrams (architecture, flowchart, sequence, UML-class, ER, agent-loop, concept-map) as SVG + PNG. Delegates rendering to the upstream [`fireworks-tech-graph`](https://github.com/yizhiyanhua-ai/fireworks-tech-graph) skill (vendored here under `skills/tech-graph/`).
-
-## Install
-
-From inside Claude Code:
-
-```text
-/plugin marketplace add <user>/agents-and-skills
-/plugin install tech-graph@drunkcoding
-```
-
-Then run `/tech-graph` (or `/tech-graph "auth flow"` to seed a topic).
-
-## Renderer Dependency
-
-The plugin needs ONE of these on your system (cairosvg recommended):
-
-| Renderer | Install |
-|----------|---------|
-| `cairosvg` | `pip install cairosvg` (Python ≥ 3.8) |
-| `rsvg-convert` | macOS: `brew install librsvg` / Debian: `apt-get install librsvg2-bin` |
-| `puppeteer` | `npm install -g puppeteer` (heavy; last resort) |
-
-Probe + auto-select:
-
-```bash
-bash plugins/tech-graph/scripts/check-deps.sh
-```
-
-The script writes the selected renderer name to `skills/tech-graph/.renderer` and skips re-probing on later runs.
-
-## Wizard Steps
-
-1. Purpose — exec-summary / engineering-review ★ / docs / blog / debug-thinking
-2. Type — architecture ★ / flowchart / sequence / UML-class / ER / agent-loop / concept-map
-3. Style — one of 7 (recommended ★ based on purpose × type)
-4. Format — SVG ★ / PNG / both
-5. Density — minimal / standard ★ / detailed
-6. Confirm — render or edit a previous step
-
-Mid-wizard you may say: `redo step 3`, `change style`, or `cancel`.
-
-## Output
-
-- Default outdir: `./diagrams/`
-- Filename: `<topic-slug>-<type>-<style>.svg` (collisions → `-2`, `-3`, …)
-
-## Optional — draw.io MCP
-
-This plugin does **not** bundle draw.io's MCP server. If you want it available alongside, add this to `~/.claude/settings.json` or your project's `.mcp.json`:
-
-```json
-{
-  "mcpServers": {
-    "drawio": { "type": "http", "url": "https://mcp.draw.io/mcp" }
-  }
-}
-```
-
-The `tech-graph` subagent does **not** depend on this MCP — it is purely opt-in.
-
-## Upstream Sync
-
-See `../../CONTRIBUTING.md` at the repo root for the `git subtree pull` workflow.

package/plugins/tech-graph/agents/tech-graph.md

@@ -1,97 +0,0 @@
----
-name: tech-graph
-description: Step-by-step wizard for generating technical diagrams (architecture, flowchart, sequence, UML, ER, agent-loop, concept-map) as SVG/PNG via the fireworks-tech-graph skill.
-tools: Read, Write, Edit, Bash, Glob, Grep
-model: sonnet
----
-
-# Tech-Graph Wizard
-
-You are a diagram wizard. Walk the user through 6 steps **one at a time**, then render an SVG (and optionally PNG) by delegating to the upstream `fireworks-tech-graph` skill at `plugins/tech-graph/skills/tech-graph/`.
-
-## Workflow
-
-Six-step wizard (purpose → type → style → format → density → confirm), then the render protocol below. Each step asks one multiple-choice question; wizard state is held as JSON in working memory until step 6.
-
-## Output
-
-An SVG (and optionally PNG) written to `<outdir>/<topic-slug>-<type>-<style>.svg`. The absolute path of every file written is reported to the user with a `snip open <path>` suggestion for visual review.
-
-## Hard Rules
-
-1. **One question per message.** Always multiple-choice. Mark the default with `★`.
-2. Never skip a step unless the user explicitly says "use defaults".
-3. Maintain wizard state in your working memory as JSON:
-   ```json
-   { "topic": "", "purpose": "", "type": "", "style": "", "format": "", "density": "", "filename": "", "outdir": "./diagrams" }
-   ```
-4. Defer reading the upstream `SKILL.md`, `references/`, `templates/` until step 6 (confirmation). At step 6, Read them, then author SVG content.
-5. **Fail fast on missing renderer.** Before authoring SVG, run `bash plugins/tech-graph/scripts/check-deps.sh`. If exit != 0, quote the script's stderr verbatim to the user and halt. Do not write any SVG.
-6. Never edit anything under `plugins/tech-graph/skills/tech-graph/` — that path is a git subtree and must stay verbatim.
-
-## The 6 Steps
-
-### Step 1 — Purpose / audience
-Ask: "What is this diagram for?"
-Options:
-- (a) exec-summary
-- (b) engineering-review ★
-- (c) docs
-- (d) blog
-- (e) debug-thinking
-
-### Step 2 — Diagram type
-Ask: "What type of diagram?"
-Options:
-- (a) architecture ★
-- (b) flowchart
-- (c) sequence
-- (d) UML-class
-- (e) ER
-- (f) agent-loop
-- (g) concept-map
-
-### Step 3 — Style
-Read `plugins/tech-graph/skills/tech-graph/references/` for the 7 upstream style references. Recommend one based on `(purpose, type)` and present all 7 with the recommendation marked `★`.
-
-### Step 4 — Format
-Ask: "Output format?"
-Options:
-- (a) SVG ★
-- (b) PNG
-- (c) both
-
-### Step 5 — Complexity / density
-Ask: "How dense should it be?"
-Options:
-- (a) minimal
-- (b) standard ★
-- (c) detailed
-
-### Step 6 — Confirm
-Show the user the full state summary, plus the resolved `filename` and `outdir`. Filename pattern: `<topic-slug>-<type>-<style>.svg`. If the file exists, append `-2`, `-3`, …
-Options: (a) yes — render, (b) edit step N, (c) cancel.
-
-## Render Protocol (after step 6 = yes)
-
-1. `bash plugins/tech-graph/scripts/check-deps.sh` — abort on failure (rule 5).
-2. Read upstream `SKILL.md` and the template files for the chosen `type`/`style`.
-3. Author the SVG content following the upstream style reference and density hint, then either:
-   - Write SVG directly to `<outdir>/<filename>`, OR
-   - Use `python3 plugins/tech-graph/skills/tech-graph/scripts/generate-from-template.py <type> <out.svg> '<json>'` when a template applies.
-4. Validate + export PNG (when format=PNG or both):
-   `bash plugins/tech-graph/skills/tech-graph/scripts/generate-diagram.sh -t <type> -s <style> -o <out.svg>`
-5. Report the absolute path of every file written. Suggest the user run `snip open <path>` for visual review.
-
-## Re-entry
-
-Accept these at any point:
-- "redo step N" — return to step N keeping all other state.
-- "change style" — return to step 3.
-- "cancel" — discard state and stop.
-
-## Failure Handling
-
-- Missing renderer → quote the `check-deps.sh` stderr verbatim, halt.
-- Upstream script non-zero exit → quote the script's stderr verbatim, halt; do not write a partial SVG.
-- Invalid SVG (validation failure) → quote validator output, halt, do not export PNG.

package/plugins/tech-graph/commands/tech-graph.md

@@ -1,13 +0,0 @@
----
-description: Step-by-step wizard for generating technical diagrams (SVG/PNG).
-argument-hint: [optional one-line topic]
----
-
-Dispatch the `tech-graph` subagent using the Agent tool. Pass `$ARGUMENTS` (which may be empty) as the initial topic seed in the subagent prompt.
-
-Subagent dispatch prompt template:
-
-> Run the tech-graph wizard. Initial topic seed: `$ARGUMENTS`.
-> Walk the user through all 6 steps even when a seed is provided. Use multiple-choice options with the marked default (★). Maintain wizard state as JSON in your working memory across turns. Do not skip steps unless the user explicitly says "use defaults".
-
-Do not perform any rendering or file generation in the main thread — the subagent owns the full wizard and the render call.

package/plugins/tech-graph/scripts/check-deps.sh

@@ -1,55 +0,0 @@
-#!/usr/bin/env bash
-# check-deps.sh — probe SVG→PNG renderers for tech-graph plugin.
-# Probes in order: cairosvg (python) → rsvg-convert (system) → puppeteer (node).
-# Writes the first available choice to skills/tech-graph/.renderer.
-# Exits 0 on success, 1 if none found (prints exact install cmd).
-
-set -euo pipefail
-
-SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
-PLUGIN_DIR="$(cd "$SCRIPT_DIR/.." && pwd)"
-RENDERER_FILE="$PLUGIN_DIR/skills/tech-graph/.renderer"
-
-probe_cairosvg() {
-  python3 -c "import cairosvg" >/dev/null 2>&1
-}
-
-probe_rsvg() {
-  command -v rsvg-convert >/dev/null 2>&1
-}
-
-probe_puppeteer() {
-  node -e "require('puppeteer')" >/dev/null 2>&1
-}
-
-if probe_cairosvg; then
-  echo "cairosvg" > "$RENDERER_FILE"
-  echo "Renderer: cairosvg (python) — selected"
-  exit 0
-fi
-
-if probe_rsvg; then
-  echo "rsvg-convert" > "$RENDERER_FILE"
-  echo "Renderer: rsvg-convert — selected"
-  exit 0
-fi
-
-if probe_puppeteer; then
-  echo "puppeteer" > "$RENDERER_FILE"
-  echo "Renderer: puppeteer (node) — selected"
-  exit 0
-fi
-
-cat <<'EOF' >&2
-ERROR: No SVG→PNG renderer found on this system.
-
-Install ONE of the following (cairosvg is recommended):
-
-  1) pip install cairosvg            # requires Python >= 3.8
-  2) brew install librsvg            # macOS
-     apt-get install librsvg2-bin    # Debian/Ubuntu
-  3) npm install -g puppeteer        # heavy; last resort
-
-After install, re-run: bash plugins/tech-graph/scripts/check-deps.sh
-EOF
-exit 1

package/plugins/tech-graph/skills/tech-graph/LICENSE

@@ -1,21 +0,0 @@
-MIT License
-
-Copyright (c) 2025 fireworks-tech-graph contributors
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.