@hasna/skills 0.1.61 → 0.1.63

package/skills/security-audit/CLAUDE.md

@@ -1,19 +0,0 @@
-# security-audit
-
-Security Audit skill.
-
-## Tech Stack
-
-- Runtime: Bun
-- Language: TypeScript
-- CLI: Commander.js
-
-## CLI
-
-```bash
-security-audit run
-```
-
-## Data Directory
-
-~/.skill/security-audit/

package/skills/security-audit/package.json

@@ -1,27 +0,0 @@
-{
-  "name": "security-audit",
-  "version": "0.1.0",
-  "description": "Security Audit skill",
-  "type": "module",
-  "bin": {
-    "security-audit": "./src/index.ts"
-  },
-  "scripts": {
-    "dev": "bun run src/index.ts",
-    "build": "bun build src/index.ts --outdir dist --target node",
-    "typecheck": "tsc --noEmit"
-  },
-  "dependencies": {},
-  "devDependencies": {
-    "@types/bun": "latest",
-    "typescript": "^5.7.0"
-  },
-  "publishConfig": {
-    "access": "restricted",
-    "registry": "https://registry.npmjs.org/"
-  },
-  "files": [
-    "src",
-    "tsconfig.json"
-  ]
-}

package/skills/security-audit/src/index.ts

@@ -1,145 +0,0 @@
-#!/usr/bin/env bun
-import { readFile, writeFile } from "fs/promises";
-import { join } from "path";
-
-function showHelp(): void {
-  console.log(`
-security-audit - Scan code for security vulnerabilities
-
-Usage:
-  skills run security-audit -- [options]
-
-Options:
-  -h, --help               Show this help message
-  path=<directory>         Directory to scan (default: current directory)
-  output=<filename>        Output report filename
-
-Detected Patterns:
-  - AWS Access Keys (CRITICAL)
-  - Private Keys (CRITICAL)
-  - Generic API Keys (HIGH)
-  - Hardcoded Passwords (HIGH)
-  - Eval Usage (MEDIUM)
-  - Insecure HTTP URLs (LOW)
-
-Output:
-  Generates a Markdown report with:
-  - Files scanned count
-  - Findings by severity
-  - File, line number, and matched content
-
-Examples:
-  skills run security-audit -- path=./src
-  skills run security-audit -- path=./src output=audit-report.md
-`);
-}
-
-const args = process.argv.slice(2);
-
-// Check for help flag
-if (args.includes("-h") || args.includes("--help")) {
-  showHelp();
-  process.exit(0);
-}
-const pathArg = args.find(a => a.startsWith("path="))?.split("=")[1] || ".";
-const outputArg = args.find(a => a.startsWith("output="))?.split("=")[1];
-
-// Simple regex patterns for demonstration
-const PATTERNS = [
-  { name: "AWS Access Key", regex: /AKIA[0-9A-Z]{16}/, severity: "CRITICAL" },
-  { name: "Private Key", regex: /-----BEGIN PRIVATE KEY-----/, severity: "CRITICAL" }, // hasna:allow-secret
-  { name: "Generic API Key", regex: /api_key\s*[:=]\s*['"][a-zA-Z0-9]{20,}['"]/, severity: "HIGH" },
-  { name: "Hardcoded Password", regex: /password\s*[:=]\s*['"][a-zA-Z0-9]{8,}['"]/, severity: "HIGH" },
-  { name: "Eval Usage", regex: /eval\(/, severity: "MEDIUM" },
-  {
-    name: "Insecure HTTP",
-    regex: /http:\/\/(?!localhost(?:[:/$]|$)|127\.0\.0\.1(?:[:/$]|$)|0\.0\.0\.0(?:[:/$]|$)|\$\{)/,
-    severity: "LOW",
-  },
-];
-
-interface Finding {
-  file: string;
-  line: number;
-  pattern: string;
-  severity: string;
-  match: string;
-}
-
-async function main() {
-  console.log(`Scanning ${pathArg}...`);
-
-  const glob = new Bun.Glob("**/*.{js,ts,json,yml,yaml,env,md,sh,bash}");
-  const files: string[] = [];
-  for await (const file of glob.scan({ cwd: pathArg })) {
-    if (
-      file.includes("/node_modules/") ||
-      file.startsWith("node_modules/") ||
-      file.includes("/.git/") ||
-      file.startsWith(".git/") ||
-      file.includes("/dist/") ||
-      file.startsWith("dist/") ||
-      file.includes("/build/") ||
-      file.startsWith("build/")
-    ) {
-      continue;
-    }
-    files.push(file);
-  }
-
-  const findings: Finding[] = [];
-
-  for (const file of files) {
-    const content = await readFile(join(pathArg, file), "utf-8");
-    const lines = content.split("\n");
-
-    for (let i = 0; i < lines.length; i++) {
-      const line = lines[i];
-      if (line.includes("regex:") && line.includes("severity:")) {
-        continue;
-      }
-      for (const pattern of PATTERNS) {
-        if (pattern.regex.test(line)) {
-          findings.push({
-            file,
-            line: i + 1,
-            pattern: pattern.name,
-            severity: pattern.severity,
-            match: line.trim().substring(0, 100) // Truncate for display
-          });
-        }
-      }
-    }
-  }
-
-  // Generate Report
-  let report = "# Security Audit Report\n\n";
-  report += `**Scan Path:** ${pathArg}\n`;
-  report += `**Files Scanned:** ${files.length}\n`;
-  report += `**Findings:** ${findings.length}\n\n`;
-
-  if (findings.length > 0) {
-    report += "| Severity | Pattern | File | Line | Match |\n";
-    report += "|---|---|---|---|---|\n";
-    for (const f of findings) {
-      report += `| ${f.severity} | ${f.pattern} | ${f.file} | ${f.line} | \`${f.match.replace(/\|/g, "\\|")}\` |\n`;
-    }
-  } else {
-    report += "✅ No vulnerabilities found.\n";
-  }
-
-  console.log(report);
-
-  if (outputArg) {
-    const outputDir = process.env.SKILLS_EXPORTS_DIR || ".";
-    const outputPath = join(outputDir, outputArg);
-    await writeFile(outputPath, report);
-    console.log(`Report saved to ${outputPath}`);
-  } else if (process.env.SKILLS_EXPORTS_DIR) {
-      // Always save a report if running in runner
-      const outputPath = join(process.env.SKILLS_EXPORTS_DIR, "security-audit-report.md");
-      await writeFile(outputPath, report);
-  }
-}
-
-main();

package/skills/security-audit/tsconfig.json

@@ -1,10 +0,0 @@
-{
-  "extends": "../tsconfig.base.json",
-  "compilerOptions": {
-    "outDir": "dist"
-  },
-  "include": [
-    "src/**/*",
-    "bin/**/*"
-  ]
-}

package/skills/security-audit-report/SKILL.md

@@ -1,52 +0,0 @@
----
-name: security-audit-report
-description: Generate a security hardening report covering auth, secrets, headers, webhooks, RLS, permissions, dependency risk, and prioritized fixes.
-kind: instruction
----
-
-# Security Audit Report
-
-Generate a security hardening package for SaaS and developer tooling projects.
-
-## Requirements
-
-None. This is an instruction skill: it is prose an agent follows, so it needs no
-credentials, no network access, and no local runtime.
-
-## Usage
-
-Ask an agent for the deliverables below and give it the inputs. Reading this file
-IS the invocation; `skills run` refuses instruction skills on purpose.
-
-## Inputs
-
-| Input | Description | Default |
-|--------|-------------|---------|
-| `target` | Directory to inspect. | current directory |
-| `scope` | Comma-separated focus areas. | auth,secrets,headers,webhooks,rls,permissions,dependencies |
-| `framework` | App stack context for recommendations. | generic web app |
-
-## Deliverables
-
-- `security-audit-report.md`
-- `findings.json`
-- `findings.csv`
-- `remediation-plan.md`
-- `manifest.json`
-
-## Method
-
-1. Scope explicitly: what you inspected, what you could not, and the date. An
-   audit silently missing a subsystem is dangerous.
-2. Work the scope areas in order (auth, secrets, transport and headers, webhooks,
-   row-level security, permissions, dependencies) and record a finding or an
-   explicit "no issue found" for each.
-3. Rate severity by exploitability and blast radius together, and justify the
-   rating in one line.
-4. For each finding: the vulnerable pattern, where it occurs, what an attacker
-   gains, and concrete remediation code or configuration.
-5. For dependency risk, run the project's own auditor (`npm audit`,
-   `bun audit`, `pip-audit`) and report its real output rather than guessing.
-6. Order the remediation plan by risk reduction per unit of effort.
-7. State clearly that this is a review, not a penetration test, and name what
-   still requires one.

package/skills/security-audit-report/package.json

@@ -1,10 +0,0 @@
-{
-  "name": "security-audit-report",
-  "version": "0.1.0",
-  "private": true,
-  "description": "Generate security hardening report artifacts",
-  "type": "module",
-  "skills": {
-    "kind": "instruction"
-  }
-}

package/skills/seo-content-pack/SKILL.md

@@ -1,54 +0,0 @@
----
-name: seo-content-pack
-description: Generate SEO content packages with topic clusters, articles, metadata, links, FAQs, and publishing cadence.
-kind: instruction
----
-
-# SEO Content Pack
-
-Generate a complete SEO content package from a topic, audience, and product context.
-
-## Requirements
-
-None. This is an instruction skill: it is prose an agent follows, so it needs no
-credentials, no network access, and no local runtime.
-
-## Usage
-
-Ask an agent for the deliverables below and give it the inputs. Reading this file
-IS the invocation; `skills run` refuses instruction skills on purpose.
-
-## Inputs
-
-| Input | Description | Default |
-|--------|-------------|---------|
-| `topic` | Core topic or search theme. Positional text also works. | required |
-| `brand` | Brand or product name. | Brand |
-| `audience` | Target audience. | SaaS buyers |
-| `articles` | Supporting article count, 3-8. | 5 |
-| `tone` | `practical`, `executive`, or `technical`. | practical |
-
-## Deliverables
-
-- `topic-cluster.md`
-- `pillar-article.md`
-- `supporting-articles/article-*.md`
-- `metadata.csv`
-- `internal-linking-plan.md`
-- `faqs.md`
-- `publishing-cadence.csv`
-- `manifest.json`
-
-## Method
-
-1. Build the topic cluster around search intent, with one pillar and supporting
-   pages that each own a distinct sub-intent. Overlapping pages cannibalize.
-2. For each page, record the primary query, the intent type, and the specific
-   question it answers better than the current top results.
-3. Write the pillar in full; outline the supporting pages to H2 level with the
-   angle each takes.
-4. Produce titles and meta descriptions within real pixel limits, front-loading
-   the query.
-5. Specify internal links in both directions with the anchor text to use.
-6. Answer FAQs in the first two sentences of each answer, then elaborate.
-7. Set a publishing cadence that matches the team's actual capacity.

package/skills/seo-content-pack/package.json

@@ -1,10 +0,0 @@
-{
-  "name": "seo-content-pack",
-  "version": "0.1.0",
-  "private": true,
-  "description": "Hosted skill metadata for seo-content-pack",
-  "type": "module",
-  "skills": {
-    "kind": "instruction"
-  }
-}

package/skills/siteanalyze/SKILL.md

@@ -1,25 +0,0 @@
-# siteanalyze
-
-Analyze any website's design system — detects shadcn/ui, Tailwind, extracts colors, typography, and components via Playwright + Claude Vision.
-
-## Usage
-
-```bash
-siteanalyze <url>
-```
-
-## What It Does
-
-- Navigates to the target URL using Playwright
-- Takes a screenshot and analyzes it with Claude Vision
-- Detects UI framework (shadcn/ui, Tailwind CSS, etc.)
-- Extracts color palette, typography scale, and component patterns
-- Outputs an open-styles compatible design profile
-
-## Output
-
-Returns a JSON design profile compatible with open-styles format, including:
-- `colors` — primary, secondary, accent, background, text colors
-- `typography` — font families, sizes, weights
-- `framework` — detected UI framework
-- `components` — identified component patterns

package/skills/siteanalyze/package.json

@@ -1,27 +0,0 @@
-{
-  "name": "siteanalyze",
-  "version": "1.0.0",
-  "description": "Analyze any website's design system — detects shadcn/ui, Tailwind, extracts colors, typography, and components",
-  "main": "src/index.ts",
-  "type": "module",
-  "bin": {
-    "siteanalyze": "src/index.ts"
-  },
-  "scripts": {
-    "start": "bun run src/index.ts"
-  },
-  "keywords": [
-    "design",
-    "shadcn",
-    "tailwind",
-    "colors",
-    "typography",
-    "playwright",
-    "analysis",
-    "open-styles"
-  ],
-  "dependencies": {},
-  "devDependencies": {
-    "@types/bun": "latest"
-  }
-}