caomeiyouren/context-analyzer
.github/skills/context-analyzer/SKILL.md
分析项目上下文、Nuxt 3 结构和依赖项，用于规划和调试。
$ install --global
skillsauthnpx skillsauth add caomeiyouren/caomei-auth context-analyzerInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 15, 2026, 4:51 PM4.2s1 file scanned
SKILL.md
- name:
- context-analyzer
- description:
- 分析项目上下文、Nuxt 3 结构和依赖项，用于规划和调试。
- version:
- 1.0.0
- author:
- GitHub Copilot
- applyTo:
- **/*.{ts,vue,json,md}
Context Analyzer Skill (上下文分析技能)
能力 (Capabilities)
- 项目结构分析: 理解 Nuxt 3/4 目录约定 (
server/api,components,pages)。 - 符号解析: 定位组件、自动导入的可组合函数 (composables) 和 TypeORM 实体的定义 (通常在
server/entities)。 - 依赖检查: 读取
package.json以验证已安装的包和版本。
指令 (Instructions)
- 读取结构: 使用目录列表工具了解布局，忽略
node_modules和.output。 - 识别后端目录: 将
server/识别为后端逻辑，包含 API (server/api), 实体 (server/entities), 工具库 (server/utils) 和数据库配置 (server/database)。 - 识别前端目录: 将
pages/components/composables/layouts识别为前端。 - 追踪逻辑: 广泛搜索符号定义，以理解数据如何在后端实体 (Entities) 和前端组件 (Components) 之间流动。
- 依赖项: 在建议导入之前检查
package.json以了解可用的库 (如dayjs,lodash-es,fs-extra)。
使用示例 (Usage Example)
输入: "分析当前的用户认证流程。"
动作: 读取 server/api/auth/*, lib/auth.ts, middleware/auth.global.ts 和 pages/login.vue 来映射流程。
Related Skills
caomeiyouren/conventional-committer
tools
VerifiedTrustedCommunity
暂存更改并生成符合 Conventional Commits 规范的提交消息。
214SKILL.mdUpdated Apr 17, 2026
openclaw/taskflow
tools
VerifiedTrustedCommunity
Use when work should span one or more detached tasks but still behave like one job with a single owner context. TaskFlow is the durable flow substrate under authoring layers like Lobster, ACPX, plugins, or plain code. Keep conditional logic in the caller; use TaskFlow for flow identity, child-task linkage, waiting state, revision-checked mutations, and user-facing emergence.
357,764SKILL.mdUpdated Apr 10, 2026
openclaw/extensions/lobster
tools
VerifiedTrustedCommunity
# Lobster Lobster executes multi-step workflows with approval checkpoints. Use it when: - User wants a repeatable automation (triage, monitor, sync) - Actions need human approval before executing (send, post, delete) - Multiple tool calls should run as one deterministic operation ## When to use Lobster | User intent | Use Lobster? | | ------------------------------------------------------ | --------------------------
357,764SKILL.mdUpdated Apr 10, 2026
steipete/extensions/lobster
tools
VerifiedTrustedCommunity
# Lobster Lobster executes multi-step workflows with approval checkpoints. Use it when: - User wants a repeatable automation (triage, monitor, sync) - Actions need human approval before executing (send, post, delete) - Multiple tool calls should run as one deterministic operation ## When to use Lobster | User intent | Use Lobster? | | ------------------------------------------------------ | --------------------------
357,588SKILL.mdUpdated Apr 13, 2026