Dayarc Add Connector

Files (1)

• SKILL.md

SKILL.md (first lines)

## When to Use

Trigger this skill when the user says anything like:
- "I need to connect Jira"
- "Add a connector for ADO / Linear / Slack"
- "Set up Jira integration"
- "I want Dayarc to check my Jira tickets"
- "Connect {tool} with requirements …"

Do NOT trigger this skill for the built-in `work-iq` or `github` connectors — those are pre-configured.

---

## Overview

This skill has five phases:
1. **Collect** — understand what the user needs from this tool
2. **Generate** — produce a custom COLLECT skill tailored to those requirements
3. **Install** — write the skill file to `~/.copilot/skills/` (upgrade-safe location)
4. **Register** — update `mcp.json` + `config.json` so the COLLECT step uses it
5. **Confirm** — show the user what was configured and what to expect in their briefs

---

## Phase 1: Collect Requirements

Ask the following questions **one at a time**. Stop asking if the user provides answers upfront.

### 1a. Tool name
If not already clear from the user's request, confirm: "Which tool are we connecting — Jira, Azure DevOps, Linear, Slack, or something else?"

### 1b. MCP server package
Ask: "What npm (or pip/Docker) package provides the MCP server for {tool}? For example, `@modelcontextprotocol/server-jira`."

For common tools, suggest defaults:
| Tool | Suggested MCP package |
|---|---|
| Jira | `@modelcontextprotocol/server-jira` |
| Azure DevOps | `@modelcontextprotocol/server-azure-devops` |
| Linear | `@modelcontextprotocol/server-linear` |
| Slack | `@modelcontextprotocol/server-slack` |

If the user doesn't know, tell them to check [modelcontextprotocol/servers](https://github.com/modelcontextprotocol/servers) or ask the tool's community.

### 1c. Signal categories
Ask: "What should Dayarc collect from {tool}? Choose all that apply:"

Present as a numbered list:
1. `assigned_items` — open tasks/tickets assigned to you (→ AM Today's Plan)
2. `notifications` — new @mentions, review requests, assignments (→ AM Today's Plan + Signals)
3. `flagged_items` — items you've starred or prioritized (→ AM Today's Plan)
4. `sent_activity` — work you've done: comments, transitions, created items (→ PM What I Did)
5. `recent_docs` — recently edited documents or wikis (→ PM What I Did)
6. `calendar` — meetings or events (→ AM/PM calendar section)
7. `saved_items` — items you've bookmarked or saved for later (→ AM Today's Plan)

Accept numbers, names, or a mix. Confirm selected categories before continuing.

### 1d. User identity
Ask: "What is your username or email address on {tool}?" (Used to scope queries to your own activity and @mentions.)

If the tool may have multiple accounts (e.g., personal + work), ask for all of them.

### 1e. Scope filters (optional)
Ask: "Are there specific projects, boards, repos, or spaces to focus on? Or should Dayarc check everything you have access to?" (If everything, leave `project_filter` empty.)

### 1f. Custom requirements (optional)
Ask: "Any other requirements? For example: 'only high-priority bugs', 'only issues in sprint', 'include status change notifications', etc."

If the user says none or skips, continue.

### 1g. MCP server credentials
Ask: "What environment variables or auth does the {tool} MCP server need? (e.g., API token, URL, email)"

For each credential: do NOT record the actual values here — just record the **variable names** (e.g., `JIRA_URL`, `JIRA_API_TOKEN`). Tell the user: "I'll add placeholder entries to `mcp.json`. You'll need to fill in the actual values there."

---

## Phase 2: Generate the COLLECT Skill

Generate a `SKILL.md` file content using the template below. Fill in all `{placeholders}` from the information collected in Phase 1.

> **Important:** The template below uses `{FOR EACH ...}` / `{END FOR EACH}` / `{IF ...}` / `{END IF}` as generation directives. **Expand these into concrete markdown sections for this specific connector.** Do not write template syntax into the output file — produce plain markdown that a human (or the agent) can read and execute directly.

```
---
name: Collect {Tool} Signals
description: Fetch {tool} signals for Dayarc COLLECT step. Generated by dayarc-add-connector on {today's date}.
---

## When to Use

Invoked by Dayarc's COLLECT step for the `{tool-lowercase}` connector when `config.json` declares `"skill": "dayarc-connect-{tool-lowercase}"`.

## Input

```json
{
  "connector": "{tool-lowercase}",
  "provides": {provides-array-json},
  "config": {config-object-json},
  "lookback": "today | 7 days",
  "since_timestamp": "ISO 8601 datetime"
}
```

## Output

Return a JSON array of normalized signals. Each signal must follow this shape:

```json
{
  "description": "One-sentence description of the signal",
  "source_breadcrumb": "URL, ticket ID, or thread subject — never blank",
  "timestamp": "ISO 8601 datetime",
  "category": "{category}",
  "connector": "{tool-lowercase}"
}
```

From YuiZhou/dayarc-agent, MIT.

More from YuiZhou/dayarc-agent