hissuno

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.

Use when analyzing a customer account - understanding their feedback history, open issues, contact activity, sentiment trajectory, and overall health. Triggers on: customer health, account review, customer deep dive, account analysis, churn risk, customer assessment, renewal prep, account health check. Requires the hissuno CLI to be configured.

Use when an issue needs prioritization analysis. Reads the issue plus linked feedback, scores it on reach/impact/confidence/effort, picks an effort estimate, and writes a product brief. Triggered manually from the issue page; also runnable on a schedule or on issue creation.

Use when a knowledge source is created to redact sensitive information (API keys, tokens, credentials, internal IPs, PII) and re-embed the source. Triggered automatically on knowledge.created.

Use when analyzing a product area or initiative - assessing demand, researching the market, evaluating competitors, and validating feasibility before committing to build. Triggers on: market analysis, initiative analysis, competitive analysis, demand validation, scope analysis, market research, TAM, competitor research. Requires the hissuno CLI to be configured.

Use when a session closes to classify the conversation with the project's feedback tags. Reads the full conversation, applies one or more of: general_feedback, wins, losses, bug, feature_request, change_request, then writes the tags back to the session. Triggered automatically on session.closed.

Use to compile a support package's wiki: re-analyze each linked knowledge source (fetch, sanitize, embed) and organize the embedded chunks into structured FAQ / how-to / feature-docs / troubleshooting markdown. Triggered manually from the support agent's package settings.

Sync HubSpot companies into Hissuno. Runs incrementally; cursor advances by hs_lastmodifieddate. OAuth refresh is handled by the credential resolver before this skill runs, so the access token in env is always fresh.

Sync HubSpot contacts into Hissuno with company association. Runs incrementally; cursor advances by lastmodifieddate.

Sync Intercom conversations into Hissuno as sessions. Runs incrementally on a schedule, advances a per-workspace cursor in automation_skill_state, and registers external→hissuno id mappings so subsequent runs skip already-synced conversations.

Sync issues from a Jira Cloud project into Hissuno. Parameterized per project — pass `projectKey` (and optionally `cloudId` if the connection has multiple sites) as run input. Cursor advances by Jira `updated` timestamp.

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.

Sync rows from a Notion database into Hissuno as issues. Parameterized: pass `databaseId` as run input. Field mapping is conservative (title from the first title property; status/priority/type defaulted). Extend the script with `fieldMapping` once a richer config surface exists.

Walk a Notion page tree (root + descendants) and ingest each page as a knowledge source under a chosen product scope. Parameterized: pass `rootPageId` and `productScopeId` as run input.

Sync PostHog persons (with identifying email) into Hissuno as contacts. Minimal version — engagement scoring and per-event signals can be added incrementally.

Handle real-time Slack events (threads, mentions, messages) for connected Slack workspaces. Fires whenever a Slack webhook lands. The full event payload is available as HISSUNO_RUN_INPUT.payload; the connection metadata is in HISSUNO_RUN_INPUT.connectionId / externalAccountId.

Sync Zendesk tickets (solved + closed) into Hissuno as sessions. Cursor advances by `updated_at` from the Zendesk Search API.

Use when working with product intelligence data: browsing feedback, tracking issues, managing customers (contacts and companies), organizing product scopes and their attached source documents, traversing the relationship graph, or connecting data sources via integrations. Works via the hissuno CLI.