平台侦察
安装方式
先用 Prompt 核对来源,也可切换到安装命令或下载可用的安装包。
用 AI 助手安装
复制提示词,让助手先核对固定版本和依赖。
查看 Prompt收起 Prompt
先检查当前 Agent 是否已安装 SkillPI Skill Finder。如果尚未安装,请按官方仓库的说明安装并启用:https://github.com/Findskills/skillpi。然后使用 Skill Finder 打开此 SkillPI 详情页并定位 "pave-recon":https://skillpi.com/zh/skills/deepskill-29e75670e9a85cfb1bdd44497e35febc5eff34aeb81d6b93d9b0bf6764de496c。安装前核对上游来源和版本:https://github.com/jeremylongshore/tons-of-skills-marketplace/blob/6ea46b08dce892944db7c16f28d0b5308d402402/plugins/ai-agency/tonone/skills/pave-recon/SKILL.md。来源不一致时停止并说明差异。核对通过后,用 Skill Finder 安装目标 Skill,并报告安装路径和来源版本。
此命令从 GitHub 来源仓库获取指定技能。运行前请先查看源文件。
npx skills add https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/6ea46b08dce892944db7c16f28d0b5308d402402/plugins/ai-agency/tonone/skills/pave-recon --skill pave-recon来源与配置
查看 GitHub 源码jeremylongshore/tons-of-skills-marketplace固定提交 6ea46b08dce892944db7c16f28d0b5308d402402
配置方式待核实
请查看原始来源中的适用工具、依赖和权限要求。
安装实测待补充
本条目介绍 平台侦察 的公开用途。DeepSkill 当前公开目录说明:“平台侦察 —— 清点所有开发工具、环境、构建系统和开发工作流,以便接管项目。当被要求“了解开发环境”、“评估开发工具”、“平台评估”或“开发人员在此如何工作”时使用。” 适用场景包括系统管理。本页根据公开目录资料和固定版本的上游仓库整理,建议使用前核对该版本的环境、工具、权限及数据处理要求。Skillπ 提供站方用途介绍与原站链接;原始 SKILL.md 和附件仅在对应许可允许时开放。
文件浏览
--- name: pave-recon description: Platform reconnaissance — inventory all developer tooling, environments, build systems, and developer workflows for project takeover. Use when asked to "understand the dev setup", "developer tooling assessment", "platform assessment", or "how do developers work here". allowed-tools: Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion version: 0.6.4 author: tonone-ai <hello@tonone.ai> license: MIT --- # Platform Reconnaissance You are Pave — the platform engineer on the Engineering Team. ## Steps ### Step 0: Detect Environment Identify project structure: - Monorepo or polyrepo? - Check for workspace configs: `pnpm-workspace.yaml`, `nx.json`, `turbo.json`, `Cargo.toml` workspaces - Check for build systems: Makefile, Justfile, Taskfile, Earthfile - Check for container setup: Dockerfile, docker-compose.yml, devcontainer.json ### Step 1: Inventory Build & Dev Tools | Tool | Purpose | Config File | Version | | -------------- | -------------- | ------------------ | ------- | | Make | Task runner | Makefile | — | | Docker Compose | Local services | docker-compose.yml | 3.x | | Nx | Monorepo | nx.json | 17.x | ### Step 2: Inventory Environments | Environment | How to Access | Provisioning | Notes | | ----------- | --------------------- | ------------ | ----- | | Local | docker-compose up | Manual | — | | Staging | deploy-staging script | CI | — | | Production | merge to main | CI | — | Check for: - Preview/ephemeral environments per PR - Environment parity (same infra as production?) - Environment variables management (`.env` files, secret manager) ### Step 3: Inventory Version Management How are tool versions managed? | Tool | Version Manager | Config File | | ------- | --------------- | --------------- | | Node.js | nvm | .nvmrc | | Python | pyenv | .python-version | | Go | mise | mise.toml | ### Step 4: Inventory Package Management | Registry | Type | Scope | Notes | | --------------- | ------- | --------------- | ------------- | | npm | Public | All JS packages | — | | GitHub Packages | Private | @org/ scoped | Internal libs | Check for: - Private registries for internal packages - Lockfile discipline (committed? up to date?) - Dependency update automation (Renovate, Dependabot) ### Step 5: Assess Developer Workflows Map standard developer flow: 1. How do new developers set up their environment? 2. How do developers run the app locally? 3. How do developers run tests? 4. How do developers create and review PRs? 5. How does code get deployed? 6. How do developers debug issues? For each step, note friction, manual steps, and tribal knowledge. ### Step 6: Deliver Assessment Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose. Output platform maturity report: | Dimension | Score (1-5) | Notes | | ------------------ | ----------- | ----- | | Local dev | ... | ... | | Build system | ... | ... | | Environments | ... | ... | | Version management | ... | ... | | Package management | ... | ... | | Developer workflow | ... | ... | | Documentation | ... | ... | | Standardization | ... | ... | Include: - Current state inventory - Biggest friction points - Quick wins for improvement - Recommended platform investments ## Key Rules - Inventory everything — tools, configs, scripts, documented and undocumented - Time developer journey — clone to running, change to deployed - Check for consistency — if 5 services use 5 different setups, that's a finding - Look for tribal knowledge — if it's not in a script or doc, it's a risk ## Delivery If output exceeds the 40-line CLI budget, invoke `/atlas-report` with the full findings. The HTML report is the output. CLI is the receipt — box header, one-line verdict, top 3 findings, and the report path. Never dump analysis to CLI.
当前收录版本
0.6.4
质量评测
满分 100。前四项来自 DeepSkill 收录的质量报告。
评分依据
提供平台工程侦察能力,帮助用户系统性地清点开发工具、环境、构建系统和工作流
评分依据
触发词精准完整,覆盖多种变体(如“了解开发环境”、“评估开发工具”等),边界清晰
评分依据
步骤划分清晰,包含 Steps、Key Rules、Delivery 等完整章节
评分依据
allowed-tools 明确且合理,覆盖文件读取、脚本执行、搜索等必要操作
计算方式
取前四项原始分值的算术平均,四舍五入取整。可通过收录报告核对各项评分与说明,运行记录需单独查证。
权限与使用前检查
根据当前主文档自动整理,命中内容可能是示例或防护说明;不是实际权限声明,也未覆盖附件、外部依赖或运行行为。
未从主文档识别到上述常见操作,不能据此判断无需权限或没有风险。
安全评级与访问范围
risk · 静态证据核验,不代表运行安全保证。
使用前请由宿主核对并授权实际文件读写、外部服务和联网目的地;本站的核验不会授予任何运行权限。
用户讨论
还没有已核实的点评。