API搜索
- 作者仓库星标 0
- 作者更新于 实时读取
- 作者仓库 nano-core
- 领域
- 通用
- 兼容 Agent
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- 信任分
- 88 / 100 · 社区维护
- 作者 / 版本 / 许可
- @0-CYBERDYNE-SYSTEMS-0 · 未声明 license
- Token 消耗评级
- 低消耗
- 接入复杂程度
- 需简单配置
- 是否需要外部 API Key
- 需要 · Google
- 兼容的系统
- macOS
- 底层运行要求
- 无特殊要求
- 文件与系统权限
-
- 只读
- 允许写入 / 修改
- Shell 执行
- 网络行为
- 允许外网请求
- 安装命令数
- 26 条
档案由构建时根据 SKILL.md 与安装命令自动衍生,可能与作者实际意图存在差异。
需要注意: 未限定 allowed-tools,默认拥有全部工具权限。
---
name: satellite-osint
description: Open satellite imagery using deeplinks with coordinates and zoom Open satellite maps via deeplin…
category: 通用
runtime: 无特殊运行时
---
# satellite-osint 输出预览
## PART A: 任务判断
- 适用问题:通用任务拆解、检查和交付。
- 输入要求:目标材料、限制条件、期望输出和验收方式。
- 证据边界:围绕“When to use this skill / When not to use this skill / 🚀 CRITICAL: Address-First Approach (FASTEST METHOD)”读取原文规则,不把推断写成作者承诺。
## PART B: 执行结果
- **01** 任务判断:确认你的需求是否属于通用任务拆解、检查和交付,并标出输入、限制和预期结果。
- **02** 执行计划:优先按“When to use this skill / When not to use this skill / 🚀 CRITICAL: Address-First Approach (FASTEST METHOD)”拆成步骤,说明每一步会读取什么、修改什么、产出什么。
- **03** 交付结果:给出可复制的命令、文件改动、检查清单或内容草稿,并说明如何继续迭代。
- **04** 风险边界:结合 读取文件、写入/修改文件、执行终端命令、会按任务需要访问外部网络、需要准备 Google API Key 给出执行前确认项。
## Running Rules
- 读取文件、写入/修改文件、执行终端命令;会按任务需要访问外部网络;需要准备 Google API Key。
- 先小样例验证,再放大到真实任务。
- 交付时同时给结果、检查口径和下一步迭代建议。 原文没有稳定的斜杠命令要求。安装验证后通常全局生效,直接在对话里点名这个 Skill 并描述任务即可。
告诉 Agent 目标文件或材料、期望结果、不可改范围、是否允许联网或执行命令。本 Skill 的权限画像是:读取文件、写入/修改文件、执行终端命令。
先用一个小任务确认它会围绕“When to use this skill / When not to use this skill / 🚀 CRITICAL: Address-First Approach (FASTEST METHOD)”工作;涉及文件或命令时,先看 diff、日志、预览或测试结果。
检查最终产物是否包含明确结果、必要证据和下一步动作;如果输出泛泛而谈,就补充输入、边界和验收标准后重跑。
---
name: satellite-osint
description: Open satellite imagery using deeplinks with coordinates and zoom Open satellite maps via deeplin…
category: 通用
source: 0-CYBERDYNE-SYSTEMS-0/nano-core
---
# satellite-osint
## 什么时候使用
- satellite-osint 是一个通用扩展技能,按 SKILL 适合处理通用任务拆解、检查、交付和复盘,核心价值是把输入、判断、执行、验证和交付边界固定下来,避免 Agent 泛泛回答。 把任务拆成可执行、可检查、可继续迭代的步骤…
- 面向通用任务拆解、检查和交付,优先处理能明确输入、步骤和验收标准的工作。
## 需要提供什么
- 目标材料、目录范围、期望结果和不可改动内容。
- 是否允许联网、执行命令、读写文件或调用外部服务。
## 执行规则
- 围绕「When to use this skill / When not to use this skill / 🚀 CRITICAL: Address-First Approach (FASTEST METHOD)」组织步骤,不把推断写成作者事实。
- 读取文件、写入/修改文件、执行终端命令;会按任务需要访问外部网络;需要准备 Google API Key。
- 先跑小样例,确认结果可检查后再扩大任务范围。
## 输出要求
- 给出最终产物、关键证据、验证方式和下一步动作。
- 信息不足时标记 unknown,不编造命令、平台或依赖。 作者原文负责流程事实;仓库文件负责来源和命令;流狐只补充适用场景、限制和质量判断。
skill "satellite-osint" {
输入层 -> 用户目标 + 目标文件 + 禁止范围 + 验收标准
上下文层 -> When to use this skill / When not to use this skill / 🚀 CRITICAL: Address-First Approach (FASTEST METHOD)
规则层 -> SKILL.md 触发条件 / 执行顺序 / 输出格式
运行层 -> 无特殊运行时 | 读取文件、写入/修改文件、执行终端命令 | 会按任务需要访问外部网络
安全层 -> 需要准备 Google API Key + 小任务验证 + diff / 日志复核
输出层 -> 可复制结果 + 检查清单 + 下一步迭代
} Satellite OSINT & Land Analysis
When to use this skill
- Use when the user request matches this skill's domain and capabilities.
- Use when this workflow or toolchain is explicitly requested.
When not to use this skill
- Do not use when another skill is a better direct match for the task.
- Do not use when the request is outside this skill's scope.
Open satellite maps via deeplinks. Capture at multiple zoom levels. Analyze land/structures.
🚀 CRITICAL: Address-First Approach (FASTEST METHOD)
ALWAYS try the address directly in the URL first. Both Google Maps and Apple Maps auto-geocode addresses - no parsing needed!
Apple Maps (Preferred - Native macOS, Fastest)
# Satellite view with address (Apple Maps auto-geocodes)
open "maps://?q=110+Clover+St+Cedar+Creek+Texas&t=h"
# Satellite view with coordinates and zoom
open "maps://?t=h&ll=30.0872,-97.5014&z=18"
Google Maps (Alternative - Browser-based)
# Satellite view with address (Google Maps auto-geocodes)
open "https://www.google.com/maps/search/110+Clover+St+Cedar+Creek+Texas/@?layer=satellite"
# Satellite view with coordinates and zoom
open "https://www.google.com/maps/@30.0872,-97.5014,18z/data=!3m1!1e3"
Force Satellite View with AppleScript
# Activate Maps and set to satellite view (Cmd+3)
osascript -e 'tell app "Maps" to activate' \
-e 'delay 1' \
-e 'tell app "System Events" to keystroke "3" using command down'
Only Geocode If:
- ❌ You need exact lat/lon for calculations
- ❌ The address format is unusual or international
- ❌ You're doing multi-location analysis with coordinates
NEVER waste tool calls geocoding when the address works directly in the URL!
Obtaining Coordinates
From Address (Geocoding - No API Key)
# Nominatim/OpenStreetMap - replace spaces with +
ADDRESS="123+Main+St,+Des+Moines,+Iowa"
curl -s "https://nominatim.openstreetmap.org/search?q=${ADDRESS}&format=json" | jq -r '.[0] | "\(.lat),\(.lon)"'
From Device Location (macOS)
# Requires Location Services enabled in System Settings > Privacy
osascript -e 'tell application "System Events" to get the value of location'
# Alternative: Use CoreLocation via swift (more reliable)
swift -e 'import CoreLocation; let m=CLLocationManager(); if let l=m.location { print("\(l.coordinate.latitude),\(l.coordinate.longitude)") }'
From IP (Approximate - Fallback)
curl -s "https://ipapi.co/json" | jq -r '"\(.latitude),\(.longitude)"'
Manual Lookup
- Google Maps: Right-click location → "What's here?" → coordinates appear at bottom
- Apple Maps: Long-press to drop pin → tap pin → coordinates in info panel
- What3Words: Convert 3-word address at what3words.com
From Property Address (Google Geocoding)
# If you have Google API key
curl -s "https://maps.googleapis.com/maps/api/geocode/json?address=123+Farm+Rd,+Iowa&key=YOUR_KEY" | jq -r '.results[0].geometry.location | "\(.lat),\(.lng)"'
URL Patterns (Use with bash open command)
Google Maps Satellite
https://www.google.com/maps/@{LAT},{LON},{ZOOM}z/data=!3m1!1e3
- ZOOM: 1-21 (21=max detail, 18=buildings clear, 15=property, 12=region)
Google Earth Web
https://earth.google.com/web/@{LAT},{LON},{ALT}a,35y,0h,0t,0r
- ALT: altitude in meters (500=high detail, 2000=overview)
Bing Maps Aerial
https://www.bing.com/maps?cp={LAT}~{LON}&lvl={ZOOM}&style=a
Sentinel Hub (Agricultural/NDVI)
https://apps.sentinel-hub.com/eo-browser/?zoom={ZOOM}&lat={LAT}&lng={LON}
ESRI World Imagery
https://www.arcgis.com/home/webmap/viewer.html?center={LON},{LAT}&level={ZOOM}
Execution Examples
Method 1: Direct Address (FASTEST)
# Apple Maps - Single command for address + satellite + screenshot
open "maps://?q=110+Clover+St+Cedar+Creek+Texas&t=h"
sleep 4
screencapture -x ~/Desktop/satellite_capture.png
Method 2: Address with Multi-Zoom (Apple Maps)
ADDRESS="110+Clover+St+Cedar+Creek+Texas"
# Regional view (zoom 12)
open "maps://?q=${ADDRESS}&t=h&z=12"
sleep 4
screencapture -x ~/Desktop/overview_z12.png
# Property level (zoom 16)
open "maps://?q=${ADDRESS}&t=h&z=16"
sleep 4
screencapture -x ~/Desktop/property_z16.png
# Structure detail (zoom 19)
open "maps://?q=${ADDRESS}&t=h&z=19"
sleep 4
screencapture -x ~/Desktop/structures_z19.png
Method 3: Coordinates with Multi-Zoom (Google Maps)
LAT=37.7749; LON=-122.4194
# Regional context
open "https://www.google.com/maps/@${LAT},${LON},12z/data=!3m1!1e3"
sleep 4
screencapture -x ~/Desktop/z12.png
# Property level
open "https://www.google.com/maps/@${LAT},${LON},16z/data=!3m1!1e3"
sleep 4
screencapture -x ~/Desktop/z16.png
# Structure detail
open "https://www.google.com/maps/@${LAT},${LON},19z/data=!3m1!1e3"
sleep 4
screencapture -x ~/Desktop/z19.png
Method 4: With AppleScript for Reliable Satellite View
# Uses AppleScript to force satellite mode and fullscreen for better quality
osascript <<'EOF'
property theAddress : "110 Clover St, Cedar Creek, Texas"
-- Open Apple Maps with satellite view
do shell script "open 'maps://?q=" & theAddress & "&t=h'"
tell application "Maps"
activate
end tell
delay 2
-- Force satellite view (Cmd+3)
tell application "System Events"
tell process "Maps"
keystroke "3" using command down
end tell
end tell
delay 4
-- Fullscreen for better screenshot
tell application "System Events"
tell process "Maps"
keystroke "f" using {command down, control down}
end tell
end tell
delay 1
-- Capture
do shell script "screencapture -x ~/Desktop/satellite_" & (do shell script "date +%Y%m%d_%H%M%S") & ".png"
EOF
Screenshot commands
screencapture -x ~/Desktop/capture.png # Silent full screen
screencapture -i ~/Desktop/selection.png # Interactive select
screencapture -T 5 -x ~/Desktop/delayed.png # 5 second delay
Visual Verification (CRITICAL STEP)
After opening the map, ALWAYS verify you're looking at the correct location!
# After capture, analyze the screenshot to confirm the address
# Use image analysis to check that the location markers and labels are correct
# If location is wrong:
# 1. Check the address spelling
# 2. Try full address with ZIP code
# 3. Use explicit coordinates instead
# 4. Re-open map and re-capture
Why This Matters:
- Last session used approximate town coordinates (Cedar Creek center) instead of actual property
- Result: 4 wrong screenshots wasted before discovery
- Prevention: Analyze first screenshot to confirm correct location before multi-zoom sequence
Complete Workflow (Agent Must Follow)
Step 1: Detect Input Type
- User provides ADDRESS → Use directly in URL (Method 1 or 2)
- User provides COORDINATES → Use in URL (Method 3)
- User says "my location" → Get device location first
Step 2: Open Map with Address/Coordinates
# Preferred: Apple Maps (faster, native)
open "maps://?q=ADDRESS&t=h"
# Alternative: Google Maps (browser-based)
open "https://www.google.com/maps/search/ADDRESS/@?layer=satellite"
Step 3: Wait for Tiles
sleep 4 # Allow satellite imagery to load fully
Step 4: Capture Screenshot
screencapture -x ~/Desktop/satellite_$(date +%Y%m%d_%H%M%S).png
Step 5: Visual Verification
# Analyze the screenshot:
# - Does it show the correct address?
# - Are the location labels visible?
# - Is the satellite view active (not road view)?
# If NO → Adjust and re-open map
Step 6: Multi-Zoom Analysis (Optional)
# If more detail needed, repeat steps 2-5 at different zoom levels:
# - zoom 12 (regional)
# - zoom 16 (property)
# - zoom 19 (structures)
Zoom Level Reference
| Zoom | View Level | Use Case |
|---|---|---|
| 10-12 | County/Region | Context, neighboring properties |
| 13-15 | Township | Property boundaries, road access |
| 16-17 | Property | Field layout, major structures |
| 18-19 | Buildings | Structure identification |
| 20-21 | Detail | Roof condition, equipment |
Provider Selection
| Need | Best Provider |
|---|---|
| General/Buildings | Google Maps |
| 3D/Terrain | Google Earth |
| Crop health/NDVI | Sentinel Hub |
| Alternative imagery | Bing Maps |
| Historical | Google Earth timeline |
Farm Analysis Workflow
- Overview (zoom 12): Regional context, access roads
- Property (zoom 16): Boundaries, field divisions
- Structures (zoom 19): Building inventory
- Crop Analysis: Use Sentinel for vegetation indices
Coordinate Format
Use Decimal Degrees (DD):
- Latitude: -90 to 90 (negative = South)
- Longitude: -180 to 180 (negative = West)
- Example: 37.7749, -122.4194
Output Organization
Save captures to organized folders:
~/Desktop/farm_analysis/
├── overview/ (zoom 10-14)
├── property/ (zoom 15-17)
├── structures/ (zoom 18-21)
Integration
Use bash tool to execute open commands. Use sleep 3-5 between URL and screenshot to allow tiles to load. Maximize browser window for best capture quality.
先判断是否适合
作者设计意图
作者的方法与取舍
边界和复核