ワンクリックでManusで任意のスキルを実行

linear-client-routing

スター3

フォーク0

更新日2026年3月3日 02:11

Reference for routing Linear issues to the correct team based on client. Use this skill whenever creating or updating Linear issues for a work.flowers client — it provides the team ID, key, and name for each client so issues land in the right place. Trigger when the user mentions creating a Linear issue, task, or ticket for any client listed here.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

work-flowers

work-flowers/skills

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

Linear Client Routing

When creating Linear issues for work.flowers clients, always look up the correct team from the table below. Use the id value as the team parameter when calling Linear tools.

Client → Team Mapping

Key	Client Name	Team ID
COGROW	co:grow	d74c31be-037d-4b02-b5fb-25e2e4dadf6b
EAA	Elite Athlete Academy	13437119-f2c0-4b3a-b9da-6ce31cd984b7
EFAI	EliteFit AI	30ae0117-d937-4cb8-9e90-f163e45edafa
GGV	Golden Gate Ventures	36053475-0bc5-4baa-8372-3c3c5aad3d1b
KNOXX	Knoxx Business Group Pty Ltd	d401de3e-0e04-49bd-8bed-02c3227e827c
MHA	Ministry of Home Affairs Singapore	cdd76c98-e4b6-4a86-bc60-effc93000449
NTUC	NTUC	d19db0ae-0f6a-40c2-96a1-970999087d3f
SCW	Secure Code Warrior	5706e4ec-8899-47be-9648-9d03edc58cb2
SKNA	Sakana AI	d13c6be4-526d-4a10-9157-a9dd91f2a83f
STA	Start Right	35200f37-11fc-46fb-ae66-7d69d9b79a7b
TS	Terrascope	88464f6d-d5a9-4d2b-8b93-037d7e50a566
WFOF	Ordinary Folk	8378580a-ac49-449d-b168-c931135f103f

Usage Rules

Match by any identifier — the user may refer to a client by full name, key, or abbreviation (e.g. "EF", "EliteFit", "EFAI" all map to EliteFit AI).
Always use the Team ID — pass the UUID from the table as the team parameter in Linear:create_issue or Linear:update_issue.
Default assignee — unless the user specifies otherwise, assign all new issues to Dennis Chiuten (user ID: bc780c50-f861-47cd-b7b6-e5dd734a75ce). Pass this UUID as the assignee parameter when calling Linear tools.
Ask if ambiguous — if the user's reference could match multiple clients, ask which one they mean before creating the issue.
Unknown clients — if a client isn't in this table, ask the user which Linear team to use rather than guessing.

Special Routing: Knoxx Foods

For Knoxx Foods (KNOXX) issues, do not use the standard Linear MCP server. Instead, use the Zapier MCP connector which provides tools for managing issues in Knoxx's Linear workspace. This gives you access to Knoxx-specific integrations and workflow automations that aren't available through the standard Linear tools.

When working on Knoxx issues:

Use Zapier:linear_create_issue, Zapier:linear_update_issue, Zapier:linear_find_issue_by_id, or Zapier:linear_find_issues_by_name instead of the standard Linear:* tools
You do not need to provide a team ID when using Zapier tools — they route directly to Knoxx's workspace
Reference the Team ID above (KNOXX: d401de3e-0e04-49bd-8bed-02c3227e827c) only if explicitly needed for context or documentation purposes

このリポジトリの他の Skills

同じリポジトリ

hero-image-generation

work-flowers/skills

Generate brand-aligned hero images for work.flowers blog posts and social content using Google Gemini via the Zapier MCP connector. Use this skill whenever Dennis asks for a hero image, blog image, social image, post visual, or any generated artwork for work.flowers content — even if he doesn't explicitly say "hero image". Trigger when the user mentions creating, drafting, or generating an image for a blog post, newsletter (Flow Statements), LinkedIn post, or any other piece of content. Also trigger when the user asks to "make an image for…", "illustrate this post", "generate a visual for…", or refers to image generation alongside Gemini, Nano Banana, Imagen, or Zapier. Walks through concept generation, prompt drafting, user approval, then calls Nano Banana Pro via Zapier and saves the result to disk.

2026-07-023

zapier-sdk

work-flowers/skills

Guide for using the Zapier SDK and CLI to explore apps, discover actions, and run authenticated API calls against 9,000+ connected apps. Trigger when the user mentions the Zapier SDK, zapier-sdk, @zapier/zapier-sdk, wants to call a connected app's API through Zapier's auth infrastructure, run a one-off action via CLI (Slack message, Google Sheet, HubSpot lookup), make authenticated fetch/curl requests through Zapier, or list connected apps. Also trigger for using the SDK inside a Code by Zapier step — the @zapier/zapier-sdk toggle, the connections[] runtime map, calling zapier.apps.X or zapier.fetch from a Code step, or collapsing a multi-branch / multi-sub-zap workflow into one Code step. This skill is for CONSUMING Zapier's pre-built connectors, NOT for BUILDING new Zapier integrations (that's zapier-platform-cli and zapier-platform-ui).

2026-06-193

notion-workers

work-flowers/skills

Guide for building Notion Workers — TypeScript programs hosted by Notion that extend Custom Agents with custom tools, sync external data into Notion databases, and receive webhook events from third-party services. Use when the user wants to build a Worker, create tools agents can call, set up syncs to pull external data into Notion, receive webhooks from external services, deploy with the ntn CLI, or configure OAuth/secrets for third-party APIs. Also trigger when the user mentions ntn, ntn workers, notionhq/workers, Notion Workers, Worker tools, Worker syncs, Worker webhooks, or wants to give a Custom Agent new capabilities beyond MCP connectors. Covers the full lifecycle: scaffolding, capability definitions, schema and builders, authentication, deployment, local testing, monitoring, and constraints. Prefer this over a standalone Notion API integration when the goal is extending a Custom Agent, receiving webhooks, or syncing external data without self-hosted infrastructure.

2026-05-133

notion-python-api

work-flowers/skills

Write and execute Python scripts that call the Notion API directly using the `notion-client` SDK. Use this skill for complex Notion operations that exceed the MCP connector's practical limits — specifically large database queries requiring pagination, cross-database relation traversal, bulk create/update operations, aggregations and counts, and data exports to CSV or markdown. Trigger whenever the user asks to query, filter, aggregate, count, summarise, export, cross-reference, or bulk-modify data across Notion databases — whether in Dennis's own workspace or a client's workspace. Also trigger when the task would require more than ~5 sequential MCP calls to complete, or when the user wants to interact with a Notion database programmatically. Do NOT trigger for simple single-page reads or writes — the Notion MCP connector handles those fine.

2026-04-243

hubspot-api-client

work-flowers/skills

Write and execute Python scripts that call the HubSpot API directly using the `hubspot-api-client` SDK. Use whenever the HubSpot MCP connector is too limited — specifically when editing records, creating or editing properties, managing lists/segments, reading or modifying workflows (flows), enrolling contacts in sequences, managing associations and pipelines, logging or reading engagements (calls/emails/notes/meetings), or working with marketing assets (emails, campaigns, forms). Trigger whenever the user asks to bulk-update, export, migrate, audit, or programmatically configure anything in a HubSpot portal. Also trigger when the task would require more than ~5 sequential MCP calls, when the user wants to create or modify a custom property, when the user mentions HubSpot lists/segments/workflows/flows/sequences, or when the user references the HubSpot API or private app token. Do NOT trigger for simple single-record reads — the HubSpot MCP connector handles those fine.

2026-04-243

content-drafting

work-flowers/skills

Draft social media posts (primarily LinkedIn) and blog articles for work.flowers. Use when Dennis asks to write, draft, or create content for LinkedIn, social media, the blog, or Flow Statements. Searches Readwise highlights for relevant themes before drafting. Saves drafts to appropriate Notion databases.

2026-04-083

name	linear-client-routing
description	Reference for routing Linear issues to the correct team based on client. Use this skill whenever creating or updating Linear issues for a work.flowers client — it provides the team ID, key, and name for each client so issues land in the right place. Trigger when the user mentions creating a Linear issue, task, or ticket for any client listed here.

Linear Client Routing

When creating Linear issues for work.flowers clients, always look up the correct team from the table below. Use the id value as the team parameter when calling Linear tools.

Client → Team Mapping

Key	Client Name	Team ID
COGROW	co:grow	d74c31be-037d-4b02-b5fb-25e2e4dadf6b
EAA	Elite Athlete Academy	13437119-f2c0-4b3a-b9da-6ce31cd984b7
EFAI	EliteFit AI	30ae0117-d937-4cb8-9e90-f163e45edafa
GGV	Golden Gate Ventures	36053475-0bc5-4baa-8372-3c3c5aad3d1b
KNOXX	Knoxx Business Group Pty Ltd	d401de3e-0e04-49bd-8bed-02c3227e827c
MHA	Ministry of Home Affairs Singapore	cdd76c98-e4b6-4a86-bc60-effc93000449
NTUC	NTUC	d19db0ae-0f6a-40c2-96a1-970999087d3f
SCW	Secure Code Warrior	5706e4ec-8899-47be-9648-9d03edc58cb2
SKNA	Sakana AI	d13c6be4-526d-4a10-9157-a9dd91f2a83f
STA	Start Right	35200f37-11fc-46fb-ae66-7d69d9b79a7b
TS	Terrascope	88464f6d-d5a9-4d2b-8b93-037d7e50a566
WFOF	Ordinary Folk	8378580a-ac49-449d-b168-c931135f103f

Usage Rules

Match by any identifier — the user may refer to a client by full name, key, or abbreviation (e.g. "EF", "EliteFit", "EFAI" all map to EliteFit AI).
Always use the Team ID — pass the UUID from the table as the team parameter in Linear:create_issue or Linear:update_issue.
Default assignee — unless the user specifies otherwise, assign all new issues to Dennis Chiuten (user ID: bc780c50-f861-47cd-b7b6-e5dd734a75ce). Pass this UUID as the assignee parameter when calling Linear tools.
Ask if ambiguous — if the user's reference could match multiple clients, ask which one they mean before creating the issue.
Unknown clients — if a client isn't in this table, ask the user which Linear team to use rather than guessing.

Special Routing: Knoxx Foods

When working on Knoxx issues:

Use Zapier:linear_create_issue, Zapier:linear_update_issue, Zapier:linear_find_issue_by_id, or Zapier:linear_find_issues_by_name instead of the standard Linear:* tools
You do not need to provide a team ID when using Zapier tools — they route directly to Knoxx's workspace
Reference the Team ID above (KNOXX: d401de3e-0e04-49bd-8bed-02c3227e827c) only if explicitly needed for context or documentation purposes