@praveencs/agent 0.9.30 → 0.10.0

package/agent-skills/skills/api-tester/skill.json

@@ -0,0 +1,16 @@
+{
+    "name": "api-tester",
+    "version": "1.0.0",
+    "description": "Test REST APIs with curl — GET, POST, PUT, DELETE with auth and headers",
+    "tools": [
+        "cmd.run"
+    ],
+    "permissions": {
+        "required": [
+            "exec",
+            "network"
+        ]
+    },
+    "entrypoint": "prompt.md",
+    "state": "approved"
+}

package/agent-skills/skills/backup/prompt.md

@@ -0,0 +1,12 @@
+Backup files and directories.
+
+## Methods
+- **tar.gz**: `tar -czf backup-$(date +%Y%m%d).tar.gz <source>`
+- **zip**: `zip -r backup-$(date +%Y%m%d).zip <source>`
+- **rsync**: `rsync -avz <source> <destination>`
+
+## Best Practices
+1. Include date in backup filename
+2. Exclude node_modules, .git, and other large directories
+3. Show backup size after completion
+4. Verify backup integrity: `tar -tzf backup.tar.gz | head`

package/agent-skills/skills/backup/skill.json

@@ -0,0 +1 @@
+{"name":"backup","version":"1.0.0","description":"Backup files and directories using tar, rsync, or zip","tools":["cmd.run"],"permissions":{"required":["exec","filesystem.read"]},"entrypoint":"prompt.md","state":"approved"}

package/agent-skills/skills/code-review/prompt.md

@@ -0,0 +1,29 @@
+Review code for quality, bugs, security, and best practices.
+
+## Steps
+1. Get the diff using `git.diff` or `git diff HEAD~1`
+2. Analyze each changed file for:
+   - **Bugs**: Logic errors, null references, off-by-one errors
+   - **Security**: SQL injection, XSS, hardcoded secrets, insecure deserialization
+   - **Performance**: N+1 queries, unnecessary loops, memory leaks
+   - **Style**: Naming conventions, code duplication, complexity
+   - **Best Practices**: Error handling, logging, input validation
+
+## Output Format
+```
+📝 Code Review Summary
+━━━━━━━━━━━━━━━━━━━━━
+Files Changed: 5
+Issues Found: 3
+
+🔴 Critical:
+  src/auth.ts:42 — API key hardcoded in source code
+
+🟡 Warning:
+  src/utils.ts:18 — Missing error handling in async function
+
+🟢 Suggestion:
+  src/index.ts:5 — Consider using destructuring assignment
+
+Overall: ⚠️ Needs attention before merge
+```

package/agent-skills/skills/code-review/skill.json

@@ -0,0 +1,18 @@
+{
+    "name": "code-review",
+    "version": "1.0.0",
+    "description": "Review code changes for bugs, best practices, and security issues",
+    "tools": [
+        "cmd.run",
+        "git.diff",
+        "fs.read"
+    ],
+    "permissions": {
+        "required": [
+            "exec",
+            "filesystem.read"
+        ]
+    },
+    "entrypoint": "prompt.md",
+    "state": "approved"
+}

package/agent-skills/skills/create-note/prompt.md

@@ -0,0 +1,21 @@
+Create formatted notes and save them as files.
+
+## Behavior
+1. Parse the user's request to extract the note topic and content
+2. Format the note with proper markdown structure:
+   - Title as H1 heading
+   - Date/time stamp
+   - Organized sections with headers
+   - Bullet points for lists
+3. Save using `fs.write` to a `.md` file
+
+## Naming Convention
+- Use kebab-case: `my-note-topic.md`
+- Save in current directory or a `notes/` folder if it exists
+- Add timestamp prefix if user requests: `2024-01-15-my-note.md`
+
+## Formatting
+- Always include a title
+- Add a date created line
+- Use proper markdown formatting
+- Include tags at the bottom if relevant: `Tags: #topic1 #topic2`

package/agent-skills/skills/create-note/skill.json

@@ -0,0 +1,15 @@
+{
+    "name": "create-note",
+    "version": "1.0.0",
+    "description": "Creates formatted notes and saves them as markdown files",
+    "tools": [
+        "fs.write"
+    ],
+    "permissions": {
+        "required": [
+            "filesystem.write"
+        ]
+    },
+    "entrypoint": "prompt.md",
+    "state": "approved"
+}

package/agent-skills/skills/cron-scheduler/prompt.md

@@ -0,0 +1,25 @@
+Manage cron jobs for scheduling tasks.
+
+## Commands
+- **List**: `crontab -l`
+- **Edit**: `crontab -e`
+- **Add job**: `(crontab -l 2>/dev/null; echo "<schedule> <command>") | crontab -`
+- **Remove all**: `crontab -r` (⚠️ dangerous, ask first)
+
+## Cron Format
+```
+┌─── minute (0-59)
+│ ┌─── hour (0-23)
+│ │ ┌─── day of month (1-31)
+│ │ │ ┌─── month (1-12)
+│ │ │ │ ┌─── day of week (0-7, Sun=0/7)
+│ │ │ │ │
+* * * * * command
+```
+
+## Common Schedules
+- Every minute: `* * * * *`
+- Every hour: `0 * * * *`
+- Daily at midnight: `0 0 * * *`
+- Every Monday 9am: `0 9 * * 1`
+- Every 5 minutes: `*/5 * * * *`

package/agent-skills/skills/cron-scheduler/skill.json

@@ -0,0 +1 @@
+{"name":"cron-scheduler","version":"1.0.0","description":"Manage cron jobs — create, list, edit, and delete scheduled tasks","tools":["cmd.run"],"permissions":{"required":["exec"]},"entrypoint":"prompt.md","state":"approved"}

package/agent-skills/skills/db-query/prompt.md

@@ -0,0 +1,12 @@
+Query databases using CLI tools.
+
+## Supported Databases
+- **SQLite**: `sqlite3 <db> "<query>"`
+- **PostgreSQL**: `psql -h <host> -U <user> -d <db> -c "<query>"`
+- **MySQL**: `mysql -h <host> -u <user> -p<pass> -e "<query>" <db>`
+
+## Safety
+- NEVER execute DROP, DELETE, or TRUNCATE without explicit user confirmation
+- Use SELECT queries by default
+- Always LIMIT results: `SELECT * FROM table LIMIT 20`
+- Show table schema first: `.schema` (SQLite) or `\d table` (PostgreSQL)

package/agent-skills/skills/db-query/skill.json

@@ -0,0 +1 @@
+{"name":"db-query","version":"1.0.0","description":"Query databases — SQLite, PostgreSQL, MySQL via CLI tools","tools":["cmd.run"],"permissions":{"required":["exec"]},"entrypoint":"prompt.md","state":"approved"}

package/agent-skills/skills/docker-deploy/prompt.md

@@ -0,0 +1,21 @@
+Build and deploy Docker containers.
+
+## Commands
+- **Build**: `docker build -t <name> .`
+- **Run**: `docker run -d -p <host>:<container> <name>`
+- **Stop**: `docker stop <container-id>`
+- **List**: `docker ps -a`
+- **Logs**: `docker logs <container-id>`
+- **Clean**: `docker system prune -f`
+
+## Docker Compose
+- **Start**: `docker-compose up -d`
+- **Stop**: `docker-compose down`
+- **Rebuild**: `docker-compose up -d --build`
+
+## Best Practices
+1. Always check if Docker is installed first: `docker --version`
+2. Check if a Dockerfile exists before building
+3. Use meaningful tag names: `<project>:<version>`
+4. Show container logs after starting to verify it's running
+5. Ask user for port mappings if not specified

package/agent-skills/skills/docker-deploy/skill.json

@@ -0,0 +1,16 @@
+{
+    "name": "docker-deploy",
+    "version": "1.0.0",
+    "description": "Builds and deploys Docker containers from Dockerfiles",
+    "tools": [
+        "cmd.run"
+    ],
+    "permissions": {
+        "required": [
+            "exec",
+            "network"
+        ]
+    },
+    "entrypoint": "prompt.md",
+    "state": "approved"
+}

package/agent-skills/skills/file-organizer/prompt.md

@@ -0,0 +1,32 @@
+Organize files in a directory by type, date, or custom rules.
+
+## Strategies
+### By File Type
+```
+Documents/ → .pdf, .doc, .docx, .txt, .md
+Images/    → .jpg, .jpeg, .png, .gif, .svg, .webp
+Videos/    → .mp4, .avi, .mkv, .mov
+Audio/     → .mp3, .wav, .flac, .aac
+Code/      → .js, .ts, .py, .go, .rs, .java
+Archives/  → .zip, .tar, .gz, .rar, .7z
+Other/     → everything else
+```
+
+### By Date
+Organize into `YYYY/MM/` folders based on file modification date.
+
+### By Project
+Group related files by detecting common prefixes or naming patterns.
+
+## Steps
+1. List all files in the target directory using `cmd.run` with `ls -la`
+2. Analyze file extensions and names
+3. Create destination folders using `cmd.run` with `mkdir -p`
+4. Move files using `cmd.run` with `mv`
+5. Report what was organized
+
+## Safety
+- Always show a preview of what will be moved BEFORE executing
+- Never organize system directories (`/`, `/usr`, etc.)
+- Skip hidden files (dotfiles) unless explicitly requested
+- Ask for confirmation before moving files

package/agent-skills/skills/file-organizer/skill.json

@@ -0,0 +1,19 @@
+{
+    "name": "file-organizer",
+    "version": "1.0.0",
+    "description": "Organizes files in a directory by type, date, or custom rules",
+    "tools": [
+        "cmd.run",
+        "fs.read",
+        "fs.write"
+    ],
+    "permissions": {
+        "required": [
+            "exec",
+            "filesystem.read",
+            "filesystem.write"
+        ]
+    },
+    "entrypoint": "prompt.md",
+    "state": "approved"
+}

package/agent-skills/skills/git-commit/prompt.md

@@ -0,0 +1,21 @@
+Automate git commits with meaningful messages.
+
+## Steps
+1. Use `git.status` to check what files have changed
+2. Use `git.diff` to see the actual changes
+3. Generate a concise, conventional commit message based on the changes
+4. Use `cmd.run` to execute:
+   - `git add .` (or specific files if the user specifies)
+   - `git commit -m "<generated message>"`
+
+## Commit Message Format
+Use conventional commits format:
+- `feat: <description>` — New feature
+- `fix: <description>` — Bug fix
+- `docs: <description>` — Documentation changes
+- `refactor: <description>` — Code refactoring
+- `chore: <description>` — Maintenance tasks
+- `style: <description>` — Formatting changes
+
+If the user provides a custom message, use that instead.
+Ask the user to confirm the commit message before executing.

package/agent-skills/skills/git-commit/skill.json

@@ -0,0 +1,17 @@
+{
+    "name": "git-commit",
+    "version": "1.0.0",
+    "description": "Stages changes and creates a git commit with a meaningful message",
+    "tools": [
+        "cmd.run",
+        "git.status",
+        "git.diff"
+    ],
+    "permissions": {
+        "required": [
+            "exec"
+        ]
+    },
+    "entrypoint": "prompt.md",
+    "state": "approved"
+}

package/agent-skills/skills/log-analyzer/prompt.md

@@ -0,0 +1,16 @@
+Analyze log files to find errors, patterns, and anomalies.
+
+## Commands
+- **Tail logs**: `tail -f <logfile>` or `tail -n 100 <logfile>`
+- **Find errors**: `grep -i "error\|fail\|exception\|fatal" <logfile>`
+- **Count by level**: `grep -c "ERROR" <logfile>`
+- **Time range**: `awk '/2024-01-15 10:00/,/2024-01-15 11:00/' <logfile>`
+- **Top errors**: `grep "ERROR" <logfile> | sort | uniq -c | sort -rn | head -10`
+
+## Output
+Provide a structured summary:
+- Total lines analyzed
+- Error count by severity (ERROR, WARN, INFO)
+- Top 5 most frequent errors
+- Timeline of error spikes (if time-stamped)
+- Recommended actions

package/agent-skills/skills/log-analyzer/skill.json

@@ -0,0 +1 @@
+{"name":"log-analyzer","version":"1.0.0","description":"Analyze log files — find errors, patterns, and anomalies","tools":["cmd.run","fs.read"],"permissions":{"required":["exec","filesystem.read"]},"entrypoint":"prompt.md","state":"approved"}

package/agent-skills/skills/npm-publish/prompt.md

@@ -0,0 +1,24 @@
+Prepare and publish npm packages.
+
+## Pre-publish Checklist
+1. Verify `package.json` has correct `name`, `version`, `main`, `types`, `bin`
+2. Ensure `files` field or `.npmignore` is configured
+3. Run `npm run build` if applicable
+4. Run `npm test` if tests exist
+5. Run `npm pack --dry-run` to preview package contents
+
+## Version Bumping
+- **Patch** (bug fixes): `npm version patch`
+- **Minor** (new features): `npm version minor`
+- **Major** (breaking changes): `npm version major`
+
+## Publishing
+```bash
+npm publish --access public    # For scoped packages
+npm publish                    # For unscoped packages
+```
+
+## Post-publish
+- Verify on npmjs.com: `npm view <package-name>`
+- Tag the release in git: `git tag v<version> && git push --tags`
+- Update CHANGELOG.md if it exists

package/agent-skills/skills/npm-publish/skill.json

@@ -0,0 +1,20 @@
+{
+    "name": "npm-publish",
+    "version": "1.0.0",
+    "description": "Prepare and publish npm packages with version bumping and changelog",
+    "tools": [
+        "cmd.run",
+        "fs.read",
+        "fs.write"
+    ],
+    "permissions": {
+        "required": [
+            "exec",
+            "network",
+            "filesystem.read",
+            "filesystem.write"
+        ]
+    },
+    "entrypoint": "prompt.md",
+    "state": "approved"
+}

package/agent-skills/skills/open-vscode/prompt.md

@@ -0,0 +1,8 @@
+Use cmd.run to open Visual Studio Code.
+
+- To open in the current directory: execute `code .`
+- To open a specific path: execute `code <path>`
+- To open in a new window: execute `code -n .`
+- To open a specific file: execute `code <filename>`
+
+Always confirm the action with the user before executing.

package/agent-skills/skills/open-vscode/skill.json

@@ -0,0 +1,15 @@
+{
+    "name": "open-vscode",
+    "version": "1.0.0",
+    "description": "Opens VS Code in the current or specified directory",
+    "tools": [
+        "cmd.run"
+    ],
+    "permissions": {
+        "required": [
+            "exec"
+        ]
+    },
+    "entrypoint": "prompt.md",
+    "state": "approved"
+}

package/agent-skills/skills/project-scaffold/prompt.md

@@ -0,0 +1,43 @@
+Scaffold new projects with proper structure and best practices.
+
+## Supported Templates
+
+### Node.js / TypeScript
+```bash
+mkdir <project> && cd <project>
+npm init -y
+npm install typescript @types/node --save-dev
+npx tsc --init
+```
+Create: `src/index.ts`, `.gitignore`, `README.md`, `tsconfig.json`
+
+### React (Vite)
+```bash
+npx -y create-vite@latest <project> --template react-ts
+```
+
+### Next.js
+```bash
+npx -y create-next-app@latest <project> --typescript --tailwind --eslint --app --src-dir
+```
+
+### Python
+```bash
+mkdir <project> && cd <project>
+python3 -m venv venv
+```
+Create: `main.py`, `requirements.txt`, `.gitignore`, `README.md`
+
+### Express API
+```bash
+mkdir <project> && cd <project>
+npm init -y
+npm install express cors dotenv
+npm install typescript @types/express @types/node --save-dev
+```
+
+## Post-Setup
+1. Initialize git: `git init`
+2. Create `.gitignore` appropriate for the project type
+3. Create a `README.md` with project name and basic setup instructions
+4. Show the project structure to the user

package/agent-skills/skills/project-scaffold/skill.json

@@ -0,0 +1,17 @@
+{
+    "name": "project-scaffold",
+    "version": "1.0.0",
+    "description": "Scaffold new projects (Node.js, Python, React, Next.js, etc.) with best practices",
+    "tools": [
+        "cmd.run",
+        "fs.write"
+    ],
+    "permissions": {
+        "required": [
+            "exec",
+            "filesystem.write"
+        ]
+    },
+    "entrypoint": "prompt.md",
+    "state": "approved"
+}

package/agent-skills/skills/send-email/prompt.md

@@ -0,0 +1,19 @@
+Send an email using the helper script.
+
+## Usage
+Run the send script using cmd.run:
+```
+node .agent/skills/send-email/send.js --to <recipient> --subject "<subject>" --body "<body>"
+```
+
+## Requirements
+- Environment variables `EMAIL_USER` and `EMAIL_PASS` must be set
+- `nodemailer` must be installed (`npm install nodemailer`)
+
+## Parameters
+- `--to`: Recipient email address (required)
+- `--subject`: Email subject line (required)
+- `--body`: Email body text (required)
+- `--html`: Send as HTML email (optional flag)
+
+If the user doesn't specify a subject, generate an appropriate one based on the body content.

package/agent-skills/skills/send-email/send.js

@@ -0,0 +1,60 @@
+#!/usr/bin/env node
+
+/**
+ * send.js — Simple email sender using nodemailer
+ * Usage: node send.js --to <email> --subject "<subject>" --body "<body>"
+ * 
+ * Requires: EMAIL_USER and EMAIL_PASS environment variables
+ */
+
+const args = process.argv.slice(2);
+
+function getArg(name) {
+    const idx = args.indexOf(`--${name}`);
+    return idx !== -1 && args[idx + 1] ? args[idx + 1] : null;
+}
+
+const to = getArg('to');
+const subject = getArg('subject');
+const body = getArg('body');
+const isHtml = args.includes('--html');
+
+if (!to || !subject || !body) {
+    console.error('Usage: node send.js --to <email> --subject "<subject>" --body "<body>" [--html]');
+    process.exit(1);
+}
+
+const user = process.env.EMAIL_USER;
+const pass = process.env.EMAIL_PASS;
+
+if (!user || !pass) {
+    console.error('Error: EMAIL_USER and EMAIL_PASS environment variables are required');
+    process.exit(1);
+}
+
+async function sendEmail() {
+    try {
+        const nodemailer = await import('nodemailer');
+
+        const transporter = nodemailer.default.createTransport({
+            service: 'gmail',
+            auth: { user, pass }
+        });
+
+        const mailOptions = {
+            from: user,
+            to,
+            subject,
+            [isHtml ? 'html' : 'text']: body
+        };
+
+        const info = await transporter.sendMail(mailOptions);
+        console.log(`✅ Email sent successfully to ${to}`);
+        console.log(`   Message ID: ${info.messageId}`);
+    } catch (error) {
+        console.error(`❌ Failed to send email: ${error.message}`);
+        process.exit(1);
+    }
+}
+
+sendEmail();

package/agent-skills/skills/send-email/skill.json

@@ -0,0 +1,16 @@
+{
+    "name": "send-email",
+    "version": "1.0.0",
+    "description": "Sends emails using nodemailer via SMTP",
+    "tools": [
+        "cmd.run"
+    ],
+    "permissions": {
+        "required": [
+            "exec",
+            "network"
+        ]
+    },
+    "entrypoint": "prompt.md",
+    "state": "approved"
+}

package/agent-skills/skills/system-monitor/prompt.md

@@ -0,0 +1,27 @@
+Monitor system resources and report health status.
+
+## Commands
+- **CPU**: `top -bn1 | head -20` or `mpstat` (if sysstat installed)
+- **Memory**: `free -h`
+- **Disk**: `df -h`
+- **Processes**: `ps aux --sort=-%cpu | head -15`
+- **Network**: `ss -tunlp` or `netstat -tunlp`
+- **Uptime**: `uptime`
+- **OS Info**: `uname -a` and `cat /etc/os-release`
+
+## Output
+Present a clean dashboard-style summary:
+```
+🖥️ System Health Report
+━━━━━━━━━━━━━━━━━━━━━
+CPU:    45% used (4 cores)
+Memory: 6.2GB / 16GB (39%)
+Disk:   120GB / 500GB (24%)
+Uptime: 3 days, 14 hours
+Top Process: node (12% CPU)
+```
+
+## Alerts
+- Flag if CPU > 80%
+- Flag if Memory > 90%
+- Flag if Disk > 85%

package/agent-skills/skills/system-monitor/skill.json

@@ -0,0 +1,15 @@
+{
+    "name": "system-monitor",
+    "version": "1.0.0",
+    "description": "Monitor system resources — CPU, memory, disk, and running processes",
+    "tools": [
+        "cmd.run"
+    ],
+    "permissions": {
+        "required": [
+            "exec"
+        ]
+    },
+    "entrypoint": "prompt.md",
+    "state": "approved"
+}

package/agent-skills/skills/web-search/prompt.md

@@ -0,0 +1,26 @@
+Search the web and extract relevant information.
+
+## Methods
+### Using curl + DuckDuckGo
+```bash
+curl -s "https://html.duckduckgo.com/html/?q=<query>" | grep -oP '(?<=<a rel="nofollow" class="result__a" href=").*?(?=")'
+```
+
+### Using curl + Google (basic)
+```bash
+curl -s "https://www.google.com/search?q=<query>" -H "User-Agent: Mozilla/5.0"
+```
+
+## Steps
+1. URL-encode the user's search query
+2. Fetch search results using curl
+3. Parse and extract relevant links and snippets
+4. Present top results in a clean, readable format
+
+## Output Format
+For each result, show:
+- **Title**: The page title
+- **URL**: The direct link
+- **Snippet**: A brief summary
+
+If the user wants to read a specific page, use `curl` to fetch and extract the main content.

package/agent-skills/skills/web-search/skill.json

@@ -0,0 +1,16 @@
+{
+    "name": "web-search",
+    "version": "1.0.0",
+    "description": "Search the web using curl and extract relevant information",
+    "tools": [
+        "cmd.run"
+    ],
+    "permissions": {
+        "required": [
+            "exec",
+            "network"
+        ]
+    },
+    "entrypoint": "prompt.md",
+    "state": "approved"
+}

package/dist/src/cli/commands/desktop.d.ts

@@ -0,0 +1,3 @@
+import { Command } from 'commander';
+export declare function createDesktopCommand(): Command;
+//# sourceMappingURL=desktop.d.ts.map

package/dist/src/cli/commands/desktop.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"desktop.d.ts","sourceRoot":"","sources":["../../../../src/cli/commands/desktop.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,OAAO,EAAE,MAAM,WAAW,CAAC;AAIpC,wBAAgB,oBAAoB,IAAI,OAAO,CAiF9C"}