[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7A52XT1TTHMQ1MMST0C7HVH":3,"skill-same:01M7A52XT1TTHMQ1MMST0C7HVH":48},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":33,"install":34,"resources":47},"01M7A52XT1TTHMQ1MMST0C7HVH","New Relic Automation",null,"Automate New Relic observability workflows -- manage alert policies, notification channels, alert conditions, and monitor applications and browser apps via the Composio MCP integration.","siuserxiaowei\u002Fxiaowei-ai-tools","siuserxiaowei","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F226641659?v=4","01M7A3SYZKS0MVRZZJQC10XSYM","siuser小伟","01M7A3SZ0735VJJQ0479SNF44J",1,"MIT","https:\u002F\u002Fgithub.com\u002Fsiuserxiaowei\u002Fxiaowei-ai-tools\u002Fblob\u002Fmain\u002Fprojects\u002F技能集合与工具目录\u002Fawesome-codex-skills\u002Fcomposio-skills\u002Fnew-relic-automation\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: New Relic Automation\ndescription: \"Automate New Relic observability workflows -- manage alert policies, notification channels, alert conditions, and monitor applications and browser apps via the Composio MCP integration.\"\nrequires:\n  mcp:\n    - rube\n---\n\n# New Relic Automation\n\nAutomate your New Relic observability workflows -- create and manage alert policies, configure notification channels (email, Slack, webhook, PagerDuty), monitor APM applications, inspect alert conditions, and integrate New Relic alerting into cross-app pipelines.\n\n**Toolkit docs:** [composio.dev\u002Ftoolkits\u002Fnew_relic](https:\u002F\u002Fcomposio.dev\u002Ftoolkits\u002Fnew_relic)\n\n---\n\n## Setup\n\n1. Add the Composio MCP server to your client: `https:\u002F\u002Frube.app\u002Fmcp`\n2. Connect your New Relic account when prompted (API key authentication)\n3. Start using the workflows below\n\n---\n\n## Core Workflows\n\n### 1. List Alert Policies\n\nUse `NEW_RELIC_GET_ALERT_POLICIES` to discover existing alert policies with optional filtering.\n\n```\nTool: NEW_RELIC_GET_ALERT_POLICIES\nInputs:\n  - name: string (optional, partial match supported)\n  - incident_preference: \"PER_POLICY\" | \"PER_CONDITION\" | \"PER_CONDITION_AND_TARGET\"\n  - page: integer (1-indexed pagination)\n```\n\n### 2. Create an Alert Policy\n\nUse `NEW_RELIC_CREATE_ALERT_POLICY` to set up a new policy container for alert conditions.\n\n```\nTool: NEW_RELIC_CREATE_ALERT_POLICY\nInputs:\n  - name: string (required) -- must be unique within the account\n  - incident_preference: \"PER_POLICY\" | \"PER_CONDITION\" | \"PER_CONDITION_AND_TARGET\" (default: PER_POLICY)\n```\n\n**Incident preferences explained:**\n- `PER_POLICY` -- one issue per policy (recommended for most use cases)\n- `PER_CONDITION` -- one issue per alert condition\n- `PER_CONDITION_AND_TARGET` -- one issue per condition and signal\u002Ftarget\n\n### 3. Create Alert Notification Channels\n\nUse `NEW_RELIC_CREATE_ALERT_CHANNEL` to register notification endpoints for alert delivery.\n\n```\nTool: NEW_RELIC_CREATE_ALERT_CHANNEL\nInputs:\n  - type: \"email\" | \"slack\" | \"webhook\" | \"pagerduty\" | \"opsgenie\" | \"victorops\" (required)\n  - name: string (required) -- human-readable channel name\n  - configuration: object (required) -- varies by type:\n    Email:     { recipients: \"devops@example.com,oncall@example.com\" }\n    Slack:     { url: \"\u003Cslack_webhook_url>\", channel: \"alerts\" }\n    Webhook:   { url: \"https:\u002F\u002Fhooks.example.com\u002Falerts\", auth_username, auth_password }\n    PagerDuty: { service_key: \"\u003Cintegration_key>\" }\n    OpsGenie:  { api_key, recipients, tags, teams }\n    VictorOps: { key: \"\u003Capi_key>\", route_key: \"\u003Crouting_key>\" }\n```\n\n### 4. Get Alert Conditions for a Policy\n\nUse `NEW_RELIC_GET_ALERT_CONDITIONS` to inspect the conditions attached to a specific policy.\n\n```\nTool: NEW_RELIC_GET_ALERT_CONDITIONS\nInputs:\n  - policy_id: integer (required)\n```\n\n### 5. Monitor Applications\n\nUse `NEW_RELIC_GET_APPLICATIONS` and `NEW_RELIC_GET_BROWSER_APPLICATIONS` to list APM and browser-monitored apps.\n\n```\nTool: NEW_RELIC_GET_APPLICATIONS\nInputs:\n  - name: string (optional, case-insensitive partial match)\n  - host: string (optional, case-insensitive partial match)\n  - ids: string (optional, comma-separated list of app IDs)\n  - page: integer (1-indexed)\n\nTool: NEW_RELIC_GET_BROWSER_APPLICATIONS\nInputs:\n  - filter[name]: string (optional, case-insensitive partial match)\n  - page: integer (1-indexed)\n```\n\n### 6. Manage Channels and Policies\n\nUse `NEW_RELIC_UPDATE_ALERT_CHANNEL` to modify existing channels and `NEW_RELIC_DELETE_ALERT_POLICY` to remove policies.\n\n```\nTool: NEW_RELIC_UPDATE_ALERT_CHANNEL\nInputs:\n  - alert_channel_id: integer (required)\n  - name: string (optional)\n  - type: string (optional, only to change type)\n  - configuration: object (optional, fields vary by type)\n\nTool: NEW_RELIC_DELETE_ALERT_POLICY\nInputs:\n  - policy_id: string (required) -- ID of the policy to delete\n```\n\n---\n\n## Known Pitfalls\n\n| Pitfall | Detail |\n|---------|--------|\n| Unique policy names | `NEW_RELIC_CREATE_ALERT_POLICY` requires the name to be unique within the account. |\n| Channel config varies by type | The `configuration` object for `NEW_RELIC_CREATE_ALERT_CHANNEL` has different required fields per channel type (e.g., `recipients` for email, `service_key` for PagerDuty). |\n| Pagination required | All list endpoints return paginated results. Iterate pages until results are exhausted. |\n| Policy ID type mismatch | `NEW_RELIC_GET_ALERT_CONDITIONS` expects `policy_id` as an integer, while `NEW_RELIC_DELETE_ALERT_POLICY` expects it as a string. |\n| Channel-policy linking | After creating a channel, you must separately associate it with a policy for alerts to flow to that channel. |\n\n---\n\n## Quick Reference\n\n| Tool Slug | Description |\n|-----------|-------------|\n| `NEW_RELIC_GET_ALERT_POLICIES` | List alert policies with optional filtering |\n| `NEW_RELIC_CREATE_ALERT_POLICY` | Create a new alert policy |\n| `NEW_RELIC_DELETE_ALERT_POLICY` | Delete an alert policy by ID |\n| `NEW_RELIC_CREATE_ALERT_CHANNEL` | Create a notification channel (email, Slack, webhook, etc.) |\n| `NEW_RELIC_GET_ALERT_CHANNELS` | List all configured alert channels |\n| `NEW_RELIC_UPDATE_ALERT_CHANNEL` | Update an existing alert channel |\n| `NEW_RELIC_GET_ALERT_CONDITIONS` | Get alert conditions for a policy |\n| `NEW_RELIC_GET_APPLICATIONS` | List APM applications |\n| `NEW_RELIC_GET_BROWSER_APPLICATIONS` | List browser-monitored applications |\n\n---\n\n*Powered by [Composio](https:\u002F\u002Fcomposio.dev)*\n","# New Relic Automation\n\nAutomate your New Relic observability workflows -- create and manage alert policies, configure notification channels (email, Slack, webhook, PagerDuty), monitor APM applications, inspect alert conditions, and integrate New Relic alerting into cross-app pipelines.\n\n**Toolkit docs:** [composio.dev\u002Ftoolkits\u002Fnew_relic](https:\u002F\u002Fcomposio.dev\u002Ftoolkits\u002Fnew_relic)\n\n---\n\n## Setup\n\n1. Add the Composio MCP server to your client: `https:\u002F\u002Frube.app\u002Fmcp`\n2. Connect your New Relic account when prompted (API key authentication)\n3. Start using the workflows below\n\n---\n\n## Core Workflows\n\n### 1. List Alert Policies\n\nUse `NEW_RELIC_GET_ALERT_POLICIES` to discover existing alert policies with optional filtering.\n\n```\nTool: NEW_RELIC_GET_ALERT_POLICIES\nInputs:\n  - name: string (optional, partial match supported)\n  - incident_preference: \"PER_POLICY\" | \"PER_CONDITION\" | \"PER_CONDITION_AND_TARGET\"\n  - page: integer (1-indexed pagination)\n```\n\n### 2. Create an Alert Policy\n\nUse `NEW_RELIC_CREATE_ALERT_POLICY` to set up a new policy container for alert conditions.\n\n```\nTool: NEW_RELIC_CREATE_ALERT_POLICY\nInputs:\n  - name: string (required) -- must be unique within the account\n  - incident_preference: \"PER_POLICY\" | \"PER_CONDITION\" | \"PER_CONDITION_AND_TARGET\" (default: PER_POLICY)\n```\n\n**Incident preferences explained:**\n- `PER_POLICY` -- one issue per policy (recommended for most use cases)\n- `PER_CONDITION` -- one issue per alert condition\n- `PER_CONDITION_AND_TARGET` -- one issue per condition and signal\u002Ftarget\n\n### 3. Create Alert Notification Channels\n\nUse `NEW_RELIC_CREATE_ALERT_CHANNEL` to register notification endpoints for alert delivery.\n\n```\nTool: NEW_RELIC_CREATE_ALERT_CHANNEL\nInputs:\n  - type: \"email\" | \"slack\" | \"webhook\" | \"pagerduty\" | \"opsgenie\" | \"victorops\" (required)\n  - name: string (required) -- human-readable channel name\n  - configuration: object (required) -- varies by type:\n    Email:     { recipients: \"devops@example.com,oncall@example.com\" }\n    Slack:     { url: \"\u003Cslack_webhook_url>\", channel: \"alerts\" }\n    Webhook:   { url: \"https:\u002F\u002Fhooks.example.com\u002Falerts\", auth_username, auth_password }\n    PagerDuty: { service_key: \"\u003Cintegration_key>\" }\n    OpsGenie:  { api_key, recipients, tags, teams }\n    VictorOps: { key: \"\u003Capi_key>\", route_key: \"\u003Crouting_key>\" }\n```\n\n### 4. Get Alert Conditions for a Policy\n\nUse `NEW_RELIC_GET_ALERT_CONDITIONS` to inspect the conditions attached to a specific policy.\n\n```\nTool: NEW_RELIC_GET_ALERT_CONDITIONS\nInputs:\n  - policy_id: integer (required)\n```\n\n### 5. Monitor Applications\n\nUse `NEW_RELIC_GET_APPLICATIONS` and `NEW_RELIC_GET_BROWSER_APPLICATIONS` to list APM and browser-monitored apps.\n\n```\nTool: NEW_RELIC_GET_APPLICATIONS\nInputs:\n  - name: string (optional, case-insensitive partial match)\n  - host: string (optional, case-insensitive partial match)\n  - ids: string (optional, comma-separated list of app IDs)\n  - page: integer (1-indexed)\n\nTool: NEW_RELIC_GET_BROWSER_APPLICATIONS\nInputs:\n  - filter[name]: string (optional, case-insensitive partial match)\n  - page: integer (1-indexed)\n```\n\n### 6. Manage Channels and Policies\n\nUse `NEW_RELIC_UPDATE_ALERT_CHANNEL` to modify existing channels and `NEW_RELIC_DELETE_ALERT_POLICY` to remove policies.\n\n```\nTool: NEW_RELIC_UPDATE_ALERT_CHANNEL\nInputs:\n  - alert_channel_id: integer (required)\n  - name: string (optional)\n  - type: string (optional, only to change type)\n  - configuration: object (optional, fields vary by type)\n\nTool: NEW_RELIC_DELETE_ALERT_POLICY\nInputs:\n  - policy_id: string (required) -- ID of the policy to delete\n```\n\n---\n\n## Known Pitfalls\n\n| Pitfall | Detail |\n|---------|--------|\n| Unique policy names | `NEW_RELIC_CREATE_ALERT_POLICY` requires the name to be unique within the account. |\n| Channel config varies by type | The `configuration` object for `NEW_RELIC_CREATE_ALERT_CHANNEL` has different required fields per channel type (e.g., `recipients` for email, `service_key` for PagerDuty). |\n| Pagination required | All list endpoints return paginated results. Iterate pages until results are exhausted. |\n| Policy ID type mismatch | `NEW_RELIC_GET_ALERT_CONDITIONS` expects `policy_id` as an integer, while `NEW_RELIC_DELETE_ALERT_POLICY` expects it as a string. |\n| Channel-policy linking | After creating a channel, you must separately associate it with a policy for alerts to flow to that channel. |\n\n---\n\n## Quick Reference\n\n| Tool Slug | Description |\n|-----------|-------------|\n| `NEW_RELIC_GET_ALERT_POLICIES` | List alert policies with optional filtering |\n| `NEW_RELIC_CREATE_ALERT_POLICY` | Create a new alert policy |\n| `NEW_RELIC_DELETE_ALERT_POLICY` | Delete an alert policy by ID |\n| `NEW_RELIC_CREATE_ALERT_CHANNEL` | Create a notification channel (email, Slack, webhook, etc.) |\n| `NEW_RELIC_GET_ALERT_CHANNELS` | List all configured alert channels |\n| `NEW_RELIC_UPDATE_ALERT_CHANNEL` | Update an existing alert channel |\n| `NEW_RELIC_GET_ALERT_CONDITIONS` | Get alert conditions for a policy |\n| `NEW_RELIC_GET_APPLICATIONS` | List APM applications |\n| `NEW_RELIC_GET_BROWSER_APPLICATIONS` | List browser-monitored applications |\n\n---\n\n*Powered by [Composio](https:\u002F\u002Fcomposio.dev)*\n",{"name":5,"requires":24,"description":7},{"mcp":25},[26],"rube","main","ebb257363024c428d3c797cb705194b35d00cb0f","projects\u002F技能集合与工具目录\u002Fawesome-codex-skills\u002Fcomposio-skills\u002Fnew-relic-automation",0,"https:\u002F\u002Fgithub.com\u002Fsiuserxiaowei\u002Fxiaowei-ai-tools","https:\u002F\u002Fgithub.com\u002Fsiuserxiaowei","2026-11-03 21:39:44",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add siuserxiaowei\u002Fxiaowei-ai-tools --skill \"New Relic Automation\"",{"tool":40,"command":41},"bunx","bunx skills add siuserxiaowei\u002Fxiaowei-ai-tools --skill \"New Relic Automation\"",{"tool":43,"command":44},"pnpm","pnpm dlx skills add siuserxiaowei\u002Fxiaowei-ai-tools --skill \"New Relic Automation\"","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsiuserxiaowei\u002Fxiaowei-ai-tools\u002Fblob\u002Fmain\u002Fprojects\u002F技能集合与工具目录\u002Fawesome-codex-skills\u002Fcomposio-skills\u002Fnew-relic-automation\u002FSKILL.md",true,[],[49,56,63,70,77,84],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":19},"01M7A66TQCYTAPVGB01H6593P0","x-article-draft-uploader","把本地 Markdown 转为经核验的 X Articles 新草稿。适用于需要保留首图封面、正文图片相对位置，并在独立 Playwright 会话中复用用户已授权 Chrome 登录态的任务；不负责公开发布。","https:\u002F\u002Fgithub.com\u002Fsiuserxiaowei\u002Fxiaowei-ai-tools\u002Fblob\u002Fmain\u002Fskills\u002Fx-article-draft-uploader\u002FSKILL.md",[],[],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7A66R643K97EQHY5AFBBVQ6","wecom-operations","通过用户已配置的官方 wecom-cli 管理企业微信文档、智能文档、待办、会议和日程。适合创建或查询这些云端对象、把本地 Markdown 转为智能文档，以及在明确确认后更新或取消对象；不发送消息、不控制桌面客户端。","https:\u002F\u002Fgithub.com\u002Fsiuserxiaowei\u002Fxiaowei-ai-tools\u002Fblob\u002Fmain\u002Fskills\u002Fwecom-operations\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7A66M3AXR54FQB7B4TX5VN9","wecom-local-vault","Inspect authorized local WeCom databases on macOS, create private plaintext snapshots, and query or export contacts, conversations, and messages without modifying the source account store. Use when the user asks to parse 企业微信\u002FWeCom local data, recover a private database snapshot, inspect local contacts or sessions, search chat history, or export a bounded conversation.","https:\u002F\u002Fgithub.com\u002Fsiuserxiaowei\u002Fxiaowei-ai-tools\u002Fblob\u002Fmain\u002Fskills\u002Fwecom-local-vault\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7A6649YFS2SQ8SKFSTBRN2Z","wechat-reading","Read and analyze WeRead\u002F微信读书 search results, book metadata, bookshelf entries, progress, notes, highlights, public reviews, recommendations, and reading statistics through the official read-only Agent Gateway. Use for WeRead account questions or exports; do not imply that the current Gateway can add, remove, upload, rate, like, or edit content.","https:\u002F\u002Fgithub.com\u002Fsiuserxiaowei\u002Fxiaowei-ai-tools\u002Fblob\u002Fmain\u002Fskills\u002Fwechat-reading\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7A65QZNA4FBYV32WH9S97QG","wechat-mp-batch-exporter","Build a bounded, private archive from known WeChat Official Account article URLs or an owner-authorized account-history export, with explicit reconciliation of article, publish-group, and platform-marked-original counts. Use for batch body capture, history normalization, or enhanced metrics\u002Fcomments workflows. Do not use for a one-page summary or to automate the WeChat client.","https:\u002F\u002Fgithub.com\u002Fsiuserxiaowei\u002Fxiaowei-ai-tools\u002Fblob\u002Fmain\u002Fskills\u002Fwechat-mp-batch-exporter\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7A65NP84R1JFFZEPVZT065P","wechat-local-vault","在 macOS 本机建立并查询私有微信数据快照。适用于盘点数据库、离线校验已有密钥候选、创建全量或增量明文快照、查会话与联系人、按时间检索消息、导出指定聊天、查看朋友圈或收藏，以及准备群聊摘要素材。所有查询只读，默认隐藏内部账号标识，不操控微信界面，也不发送任何内容。","https:\u002F\u002Fgithub.com\u002Fsiuserxiaowei\u002Fxiaowei-ai-tools\u002Fblob\u002Fmain\u002Fskills\u002Fwechat-local-vault\u002FSKILL.md",[],[]]