Skills de Claude Code · página 51

Ensure Persistent logs is setup and configured to S3

Ensure access logs are enabled

Ensure that HTTPS is enabled on load balancer

Ensure customer-managed keys are used to encrypt AWS Fargate ephemeral storage data for Amazon ECS

Ensure AWS Config is Enabled for Lambda and Serverless

Ensure Lambda functions do not allow unknown cross account access via permission policies

Ensure that the runtime environment versions used for your Lambda functions do not have end of support dates

Ensure encryption in transit is enabled for Lambda environment variables

Ensure Cloudwatch Lambda insights is enabled

Ensure AWS Secrets manager is configured and being used by Lambda for databases

Ensure least privilege is used with Lambda function access

Ensure every Lambda function has its own IAM Role

Ensure Lambda functions are not exposed to everyone

Ensure Lambda functions are referencing active execution roles

Ensure that Code Signing is enabled for Lambda functions

Ensure there are no Lambda functions with admin privileges within your AWS account

Ensure communications between your applications and clients is encrypted

Ensure Consistent Naming Convention is used for Organizational AMI

Ensure Amazon Machine Images (AMIs) are encrypted

Ensure Only Approved Amazon Machine Images (AMIs) are Used

Ensure Images (AMI) are not older than 90 days

Ensure Images are not Publicly Available

Ensure unused ENIs are removed

Ensure instances stopped for over 90 days are removed

Ensure EBS volumes attached to an EC2 instance are marked for deletion upon instance termination

Ensure Secrets and Sensitive Data are not stored directly in EC2 User Data

Ensure EC2 Auto Scaling Groups Propagate Tags to EC2 Instances that it launches

Ensure EBS volume encryption is enabled

Ensure Public Access to EBS Snapshots is Disabled

Ensure EBS volume snapshots are encrypted

Ensure unused EBS volumes are removed

Ensure Tag Policies are Enabled

Ensure an Organizational EC2 Tag Policy has been Created

Ensure no AWS EC2 Instances are Older than 180 days

Ensure detailed monitoring is enabled for production EC2 Instances

Ensure Default EC2 Security groups are not being used

Ensure the Use of IMDSv2 is Enforced on All Existing Instances

Ensure use of AWS Systems Manager to manage EC2 instances

Ensure Amazon ECS task definitions using 'host' network mode do not allow privileged or root user access to the host

Ensure Amazon ECS services are tagged

Ensure Amazon ECS clusters are tagged

Ensure Amazon ECS task definitions are tagged

Ensure only trusted images are used with Amazon ECS

Ensure 'assignPublicIp' is set to 'DISABLED' for Amazon ECS task sets

Ensure 'assignPublicIp' is set to 'DISABLED' for Amazon ECS services

Ensure Amazon ECS task definitions do not have 'pidMode' set to 'host'

Ensure Amazon ECS task definitions do not have 'privileged' set to 'true'

Ensure 'readonlyRootFilesystem' is set to 'true' for Amazon ECS task definitions

Ensure secrets are not passed as container environment variables in Amazon ECS task definitions

Ensure logging is configured for Amazon ECS task definitions

Ensure Amazon ECS Fargate services are using the latest Fargate platform version

Ensure monitoring is enabled for Amazon ECS clusters

Apply updates to any apps running in Lightsail

Enable storage bucket access logging

Ensure your Windows Server based lightsail instances are updated with the latest security patches

Change the auto-generated password for Windows based instances

Change default Administrator login names and passwords for applications

Disable SSH and RDP ports for Lightsail instances when not needed

Ensure SSH is restricted to only IP address that should have this access

Ensure RDP is restricted to only IP address that should have this access

Disable IPv6 Networking if not in use within your organization

Ensure you are using an IAM policy to manage access to buckets in Lightsail

Ensure Lightsail instances are attached to the buckets

Ensure that your Lightsail buckets are not publicly accessible

Ensure you are using VPC Endpoints for source code access

Ensure AWS Batch is configured with AWS CloudWatch Logs

Ensure Batch roles are configured for cross-service confused deputy prevention

Ensure Data Ingestion is Secure

Ensure Database has automated Backups enabled

Ensure Data at Rest is Encrypted

Ensure Encryption in Transit is Configured

Ensure Access Control and Authentication is Enabled

Ensure Fine-Grained Access Control is Enabled

Ensure Audit Logging is Enabled

Ensure Regular Updates and Patches are Installed

Ensure Monitoring and Alerting is Enabled

Ensure to Review and Update the Security Configuration

Ensure to Implement Identity and Access Management (IAM)

Ensure Network Access is Secure

>

Use when the user asks to draft, polish, translate, or reply to an email. Produces a clean draft with subject line, greeting, body, and sign-off, plus a pre-send self-check.

Use when the user mentions 飞书 / Feishu / Lark workspace operations: docx (云文档) read/write, bitable (多维表格) records / views / dashboards, drive (云盘) upload/download, wiki (知识库) link resolution, approval (审批) instance create/cancel/query, calendar (日历) event create/list/update + attendees, contact (联系人) user/department lookup, hire (招聘) job/talent/application listing. Trigger on phrases like 'OKR 周报', '把这份文档发到飞书云盘', '给团队拉个评审会议', '查 [姓名] 的联系方式', '撤销那条审批', '/wiki 链接', or any request that mentions a feishu / lark URL / token (doxcn.../bascn.../wikcn.../boxcn.../om_...).

Hope Agent browser automation — the standard `status → tabs → snapshot → act` loop, stale-ref recovery rules, and what to do when login / 2FA / captcha / camera-prompt / dialog blocks progress. Load this skill whenever you reach for the `browser` tool. Trigger on: user asks the agent to open / control / click / scrape / log into / verify something in a web app ('open X and click Y', '打开 X 然后点击 Y', 'log into my Gmail', 'scrape this page', 'fill out the form on X'); user reports a flow that requires real browser context (cookies, JS-rendered content, OAuth).

Discover and install third-party skills from external registries when the user needs a capability that no currently-active skill covers. Trigger when: (1) the user explicitly asks 'find a skill for X', 'is there a skill that does X', 'install a skill to X', (2) the user requests a well-known integration (Slack, Notion, Trello, GitHub, Hue, Sonos, iMessage, weather, TTS, transcription …) that isn't in the active skill catalog, (3) you are about to hand-write ad-hoc shell / API code for a domain that almost certainly has a published skill. Do NOT trigger if an active skill already covers the need — scan the visible skill catalog first.

Self-service diagnostics — query Hope Agent's local SQLite databases (logs / sessions / background jobs) directly via the `exec` tool to investigate problems, analyze usage, and locate root causes. Trigger on: user reports something broken / failing / slow / stuck / not responding ('X 不工作', 'X 报错', 'X 卡住', '为什么 X 失败', 'why did X fail', 'show me the logs', 'check what happened'); ad-hoc data analysis ('this week's token usage', '最近调用最多的工具', 'how many subagent runs failed', 'tool error rate', 'find sessions where X happened'); verifying a fix ('did the error stop after I changed Y'). Use BEFORE asking the user to paste log snippets — the data is on disk, query it directly. Read-only — SELECT only, never UPDATE/DELETE/INSERT/DROP.

Hope Agent native macOS desktop control — the standard `mac_control` status / diagnostics / apps / dock / spaces / snapshot / visual / windows / menu / clipboard / dialog loop, target-first action rules, no-blind-coordinate policy, and recovery for stale AX/window/menu/dialog state. Load whenever using `mac_control`, or when the user asks to control local Mac apps, Dock, Spaces, click/type/menu/window/dialog/clipboard, automate Finder/TextEdit/System Settings, visually locate UI, or says 控制 Mac, macOS 自动化, 点按钮, 打开应用, Dock, Space, 关闭窗口, 菜单点击, 视觉定位.

Self-understanding and issue reporting for Hope Agent itself. Use when the user asks how Hope Agent works internally, asks about its own source code/docs/runtime behavior, reports a bug/failure/slowness/crash, asks to diagnose logs, or asks to create/submit a GitHub issue for a bug, feature request, or improvement (including when there is no bug). Chinese triggers: 自查, 了解自己, 自我诊断, 排查 Hope Agent, 提交 issue, 需求 issue, 功能改进.

Check for and install Hope Agent updates through conversation. Use whenever the user asks about upgrades, new versions, release notes, or reports a bug that might already be fixed upstream — phrases like 'upgrade Hope Agent', 'update hope agent', 'check for new version', '升级一下', '有新版本吗', '帮我升级', 'is there a newer build', 'check release notes', 'install the latest'. Also use proactively when an `app_update(action=\"check\")` result shows `has_update: true` and the user hasn't been told yet. Covers all three formfactors: desktop GUI bundle (DMG/MSI/AppImage), `hope-agent server` daemon installed via Homebrew/Scoop/AUR/apt/dnf, and headless single-binary deployments. The upgrade is always user-confirmed via `ask_user_question` — never silent.

Manage Hope Agent application settings through conversation. Use when the user wants to view or change any app configuration: theme, language, proxy, temperature, notifications, tool timeout, context compaction, automatic session titles, web search, GitHub issue reporting, memory, embedding, multimodal embedding, dreaming (offline memory consolidation), recap, behavior awareness, smart-mode approvals, plan mode, ask-user-question timeout, tool-result disk spill threshold, embedded server, ACP control plane, MCP subsystem (kill switch / concurrency / backoff), per-skill env vars, or any other setting visible in the Settings UI. Trigger phrases: 'change settings', 'configure proxy', 'set theme to dark', 'turn off notifications', 'adjust temperature', 'show my settings', 'bind the server to all interfaces', 'enable smart mode', 'tune dreaming', 'disable mcp', 'show my channels'. Trigger even when the user doesn't explicitly say 'settings' — any intent to adjust app behavior qualifies.

Create, edit, improve, or audit Hope Agent skills. Use when the user wants to: (1) create a new skill from scratch, (2) edit or improve an existing skill, (3) review or clean up a SKILL.md file, (4) run evaluations to test skill effectiveness, (5) optimize skill descriptions for better trigger accuracy. Trigger phrases: 'create a skill', 'make a skill', 'improve this skill', 'review skill', 'audit skill'.

Use when the user asks to capture, structure, or summarize meeting notes / call notes / 1:1 discussion / standup notes. Produces a standard template with attendees, agenda, decisions, action items (owner + deadline), and open questions.

Use when the user asks for a flowchart, architecture diagram, sequence diagram, ER diagram, state machine, gantt chart, or any visual that fits Mermaid syntax. Hope Agent's chat renders Mermaid blocks natively, so the diagram appears inline.

Use when the user asks to create, edit, inspect, polish, verify, or deliver Word `.docx` documents, Google Docs-targeted drafts, business briefs, forms, reports, tables, checklists, redraft-ready document sections, or PDF/Word source-to-DOCX transformations.

Use when the user asks to create, inspect, verify, polish, or deliver PowerPoint `.pptx` decks, Google Slides-targeted deck artifacts, strategy narratives, operating reviews, pitch decks, teaching decks, section slides, bullet slides, or source-to-PPTX transformations.

Use when the user asks to create, inspect, verify, analyze, format, or deliver Excel `.xlsx` workbooks, Google Sheets-targeted spreadsheet artifacts, trackers, budgets, models, tables, dashboards, formulas, CSV/TSV-to-XLSX conversions, or spreadsheet-ready data packs.

Use when the user asks for a weekly / monthly status report, project update, individual or team progress summary. Produces a tight, scannable update with what shipped, what's in flight, what's blocked, and metrics.

Use when executing implementation plans with independent tasks. Dispatches fresh subagent per task with two-stage review (spec compliance then code quality).

Use when encountering any bug, test failure, or unexpected behavior. 4-phase root cause investigation — NO fixes without understanding the problem first.

Use when implementing any feature or bugfix, before writing implementation code. Enforces RED-GREEN-REFACTOR cycle with test-first approach.

Use when you have a spec or requirements for a multi-step task. Creates comprehensive implementation plans with bite-sized tasks, exact file paths, and complete code examples.