Menu
Sync issues from a Linear team into Hissuno. Runs incrementally on a schedule, advances a per-team cursor in automation_skill_state, and registers external→hissuno id mappings so subsequent runs skip already-synced issues.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Sync Fathom meetings (recorded calls + transcripts) into Hissuno as sessions. Cursor advances by `created_at`.
Register a GitHub repository as a Hissuno codebase. Parameterized: pass `repoFullName` and optional `branch`. Verifies the repo (and branch, if provided) is reachable, then POSTs to /api/codebases. Re-running is idempotent — duplicate codebases on the same (project, repo, branch) are filtered server-side.
Sync GitHub issues from a repository as feedback sessions. Parameterized: pass `repoFullName` (owner/repo) as run input. Cursor advances by issue `updated_at`. Pulls comments inline so each session has the full thread.
Handle GitHub App installation lifecycle webhooks (installation created, deleted, repositories added/removed). Records the change so the integrations UI can react. The github plugin's other webhooks (issues, pulls) should trigger their own skills as the migration progresses.
Sync Gong calls (recorded sales calls + transcripts) into Hissuno as sessions. Cursor advances by call started date.
Use when picking the next development issue to work on and implementing it end-to-end. This skill is the body of a continuous development loop - it selects the highest-priority ready issue from Hissuno, implements it, and creates a PR. Triggers on: next issue, continuous development, dev loop, what to build next, pick next task, implement next issue, development queue. Requires the hissuno CLI to be configured.
| name | linear-issues |
| description | Sync issues from a Linear team into Hissuno. Runs incrementally on a schedule, advances a per-team cursor in automation_skill_state, and registers external→hissuno id mappings so subsequent runs skip already-synced issues. |
| version | 1.0 |
| license | MIT |
| metadata | {"author":"hissuno"} |
| triggers | {"manual":{},"scheduled":{"cron":"0 */6 * * *"}} |
| capabilities | {"sandbox":true,"webSearch":false} |
| requires | {"plugins":["linear"]} |
| input | {"teamId":{"type":"string","required":true,"description":"Linear team id to sync issues from."}} |
| timeoutMs | 1200000 |
Pulls issues from one Linear team into Hissuno's issues resource.
HISSUNO_RUN_INPUT.teamId.updatedAtSince) from automation_skill_state for this skill, keyed by team id./api/issues with external_id + external_source = 'linear' so the resource POST endpoint registers the external→hissuno mapping.updatedAt from this run) back to automation_skill_state.tsx scripts/sync.ts
The script expects these env vars (the sandbox harness injects them):
LINEAR_ACCESS_TOKEN — provided by requires.plugins: [linear]HISSUNO_API_KEY, HISSUNO_PROJECT_ID, HISSUNO_RUN_INPUT, HISSUNO_SKILL_IDHISSUNO_BASE_URL — defaults to http://localhost:3000 if absentWhen the script finishes, write a one-line JSON summary to output.json:
{ "synced": 12, "skipped": 4, "cursor": "2026-05-06T12:00:00Z" }
That summary becomes automation_runs.output.