@farazirfan/costar-server-executor 1.7.17 → 1.7.20

package/skills/skill-creator/SKILL.md

@@ -1,236 +0,0 @@
----
-name: skill-creator
-description: "Create new skills for the CoStar agent. Use when the user wants to add a new reusable capability, automate a workflow, or improve the agent's abilities. Also use when the agent identifies a repeating pattern that should be turned into a skill."
-metadata:
-  emoji: "🛠️"
-  always: true
-  skillKey: skill-creator
----
-
-# Skill Creator
-
-You can create new skills to extend your own capabilities. Skills are modular, reusable instructions that teach you how to handle specific tasks.
-
-## What is a Skill?
-
-A skill is a directory containing a `SKILL.md` file with:
-1. **YAML frontmatter** - metadata (name, description, requirements)
-2. **Markdown body** - detailed instructions for the agent to follow
-
-Skills can also include:
-- `scripts/` - executable scripts (Python, Bash, etc.)
-- `references/` - documentation files to load into context
-- `assets/` - templates, configs, or other files
-
-## Skill Locations
-
-Skills can be installed in three places:
-
-| Location | Path | Scope |
-|----------|------|-------|
-| **Workspace** | `<workspace>/skills/<name>/` | This agent only |
-| **Managed** | `~/.costar/skills/<name>/` | All agents on this machine |
-| **Bundled** | Shipped with the package | All installations |
-
-**Recommendation**: Create skills in the **workspace** (`skills/` subdirectory) for user-specific skills, or in **managed** (`~/.costar/skills/`) for skills that should persist across workspace resets.
-
-## Creating a New Skill
-
-### Step 1: Plan the Skill
-
-Before creating, consider:
-- **What task does it automate?** Be specific.
-- **What tools/commands does it need?** List required binaries, APIs, or env vars.
-- **Is it reusable?** Skills should handle a class of tasks, not one-off actions.
-- **What scripts or references would help?** Think about helper scripts.
-
-### Step 2: Create the Directory Structure
-
-```bash
-# For workspace skills:
-mkdir -p <workspace>/skills/<skill-name>
-
-# For managed skills (shared):
-mkdir -p ~/.costar/skills/<skill-name>
-```
-
-### Step 3: Write SKILL.md
-
-Create `SKILL.md` with this template:
-
-```markdown
----
-name: my-skill-name
-description: "Clear, one-line description of what this skill does and when to use it."
-metadata:
-  emoji: "🔧"
-  requires:
-    bins: ["required-binary"]
-    env: ["REQUIRED_ENV_VAR"]
-  install:
-    - kind: brew
-      formula: required-binary
-    - kind: npm
-      package: required-package
----
-
-# Skill Name
-
-## Overview
-Brief explanation of what this skill does.
-
-## Instructions
-Step-by-step instructions for the agent to follow when this skill is activated.
-
-### Step 1: ...
-### Step 2: ...
-
-## Examples
-Show example inputs and expected outputs.
-
-## Notes
-Any caveats, edge cases, or important considerations.
-```
-
-### Step 4: Add Resources (Optional)
-
-```
-my-skill/
-├── SKILL.md
-├── scripts/
-│   ├── helper.py      # Helper scripts
-│   └── setup.sh       # Setup script
-├── references/
-│   └── api-docs.md    # Reference documentation
-└── assets/
-    └── template.json  # Template files
-```
-
-### Step 5: Validate
-
-After creating the skill:
-1. Check it appears in the skills list (the agent will see it on next turn)
-2. Test it by asking the agent to use it
-3. Iterate on the instructions based on results
-
-## YAML Frontmatter Reference
-
-### Required Fields
-
-| Field | Type | Description |
-|-------|------|-------------|
-| `name` | string | Unique skill identifier (lowercase, hyphens) |
-| `description` | string | When to use this skill (shown to agent) |
-
-### Optional Metadata Fields
-
-| Field | Type | Description |
-|-------|------|-------------|
-| `emoji` | string | Display emoji |
-| `always` | boolean | Always load (skip requirement checks) |
-| `skillKey` | string | Config key override |
-| `primaryEnv` | string | Primary API key env var |
-| `os` | string[] | Supported OS: `["darwin", "linux"]` |
-| `requires.bins` | string[] | Required binaries (all must exist) |
-| `requires.anyBins` | string[] | Required binaries (at least one) |
-| `requires.env` | string[] | Required environment variables |
-| `install` | array | Installation specs |
-
-### Install Specs
-
-```yaml
-install:
-  - kind: brew        # macOS Homebrew
-    formula: package-name
-  - kind: npm         # Node.js package
-    package: package-name
-  - kind: apt         # Debian/Ubuntu package
-    package: package-name
-  - kind: download    # Direct download
-    url: https://...
-    bins: ["binary-name"]
-```
-
-## Self-Improvement Guidelines
-
-When you notice a repeating pattern or workflow that could benefit from a skill:
-
-1. **Identify the pattern** - What steps are repeated? What's the common input/output?
-2. **Abstract it** - Generalize specific details into parameters
-3. **Create the skill** - Write clear, reusable instructions
-4. **Save it** - Put it in the workspace or managed skills directory
-5. **Announce it** - Tell the user you've created a new skill
-
-### Good Candidates for Skills
-- Multi-step workflows you've done more than twice
-- Complex tool chains (e.g., "search web → summarize → email results")
-- Domain-specific knowledge (e.g., "deploy to production checklist")
-- User-specific preferences (e.g., "format reports the way I like them")
-
-### Bad Candidates for Skills
-- One-off tasks
-- Simple single-tool operations
-- Tasks that change significantly each time
-
-## Examples of Well-Written Skills
-
-### Example: Daily Briefing Skill
-
-```markdown
----
-name: daily-briefing
-description: "Compile and send a daily briefing with calendar events, important emails, and task updates."
-metadata:
-  emoji: "📋"
-  requires:
-    env: ["GOOGLE_SERVICE_ACCOUNT_JSON"]
----
-
-# Daily Briefing
-
-## Instructions
-1. Get today's calendar events using get_calendar_events
-2. Search for unread important emails using search_emails
-3. Check pending cron jobs using cron tool status
-4. Compile into a concise briefing
-5. Send via message tool to the user
-
-## Format
-Subject: Daily Briefing - {date}
-
-📅 Calendar:
-- {event1}
-- {event2}
-
-📧 Important Emails:
-- {email1}
-- {email2}
-
-✅ Tasks:
-- {task1}
-```
-
-### Example: Code Review Skill
-
-```markdown
----
-name: code-review
-description: "Review code changes for bugs, style issues, and improvements."
-metadata:
-  emoji: "🔍"
-  requires:
-    bins: ["git"]
----
-
-# Code Review
-
-## Instructions
-1. Run `git diff` to see changes
-2. Analyze each file for:
-   - Bugs or logic errors
-   - Style inconsistencies
-   - Missing error handling
-   - Security issues
-3. Provide structured feedback with severity levels
-4. Suggest specific improvements with code examples
-```

package/skills/test/SKILL.md

@@ -1,57 +0,0 @@
----
-name: test
-description: Run tests using common testing frameworks (vitest, jest, npm test). Verify code quality before committing.
-metadata:
-  emoji: "🧪"
-  requires:
-    anyBins: ["npm", "pnpm", "yarn", "bun"]
----
-
-# Test Skill
-
-Run tests and verify code quality.
-
-## Running Tests
-
-**All tests:**
-```bash
-npm test
-```
-
-**Watch mode:**
-```bash
-npm test -- --watch
-```
-
-**Single file:**
-```bash
-npm test -- path/to/test.ts
-```
-
-**Coverage:**
-```bash
-npm test -- --coverage
-```
-
-## Best Practices
-
-1. **Run tests before committing**: Always verify tests pass
-2. **Write tests for new features**: Cover new code paths
-3. **Fix failing tests first**: Don't commit broken tests
-4. **Check coverage**: Aim for good test coverage on critical paths
-5. **Watch mode during development**: Use `--watch` for faster feedback
-
-## Common Testing Patterns
-
-**Unit tests**: Test individual functions/modules in isolation
-
-**Integration tests**: Test components working together
-
-**E2E tests**: Test full user workflows
-
-## Tips
-
-- Run specific test suites: `npm test -- --grep "pattern"`
-- Update snapshots: `npm test -- --update` (use carefully)
-- Verbose output: `npm test -- --verbose`
-- Parallel execution: Most frameworks run tests in parallel by default