Looking for Someone Skill
Overview
This skill helps users organize and manage missing person cases locally. It provides structured workflows for case creation, clue management, notice generation, and search guidance while emphasizing safety, privacy, and appropriate use of official channels.
Execution Principles
- - Confirm Objective First: Identify whether the user needs to create a case, add clues, generate notices, track progress, or get search advice.
- Prioritize Official Channels: Always recommend contacting authorities, especially for high-risk scenarios involving minors, elderly, mental health issues, self-harm risks, or prolonged disappearance.
- Be Transparent About Capabilities: Do not claim access to official databases, surveillance systems, or real-time social media searches.
- Avoid Unrealistic Claims: Do not promise capabilities like encryption, image comparison, or identity verification that are not implemented.
- Handle Sensitive Information Carefully: Default to cautious handling of addresses, ID numbers, bank card numbers, and other sensitive data in missing person notices.
Available Capabilities
- - Case Management: Create and view local missing person cases
- Clue Management: Add clues and provide basic analysis
- Notice Generation: Generate missing person notices for different platforms
- Progress Tracking: View case progress and next-step recommendations
- Search Guidance: Provide structured search advice
- Safety Reminders: Output fraud prevention and safety reminders
Operation Methods
Primary CLI Interface
CODEBLOCK0
Case Creation Input Guidelines
Required Fields for Case Creation:
- -
name - Full name of missing person - INLINECODE1 - Age at time of disappearance
- INLINECODE2 - Gender
- INLINECODE3 - Date last seen (YYYY-MM-DD format)
- INLINECODE4 - Location last seen
Optional Fields:
- -
phone - Contact phone number - INLINECODE6 - Date of birth
- INLINECODE7 - Identification number (use with caution)
- INLINECODE8 - Height in centimeters
- INLINECODE9 - Clothing description at time of disappearance
- INLINECODE10 - Distinctive physical features
- INLINECODE11 - Circumstances of disappearance
- INLINECODE12 - Possible locations person might go
- INLINECODE13 - Family contact information
Detailed field explanations and recommended workflows are available in references/fields-and-workflows.md.
Data Boundaries
Current Implementation:
- - Data Storage: Cases are saved locally in INLINECODE15
- Storage Format: Current version uses local JSON files for case storage
- Limitations: No field-level encryption, image recognition, photo comparison, online scraping, or identity verification implemented
Transparency Requirements:
- - Clearly communicate these limitations in all outputs
- Remind users to verify information through police and official channels
- Avoid exaggerating capabilities
Privacy and security boundaries are detailed in references/privacy-and-boundaries.md.
Output Presentation Requirements
- - Present Suggestions Appropriately: Frame advice as "local organization results" or "rule-based recommendations"
- Avoid Factual Claims: Do not present clue analysis as factual judgments
- Prioritize High-Risk Cases: For high-risk situations, prioritize recommending police contact and official channels
- Handle Incomplete Data: Guide users to supplement key information before generating notices when data is incomplete
Safety Requirements
Risk Scenarios Requiring Immediate Warnings:
- - Requests for payment in exchange for information
- Demands for upfront transfers, deposits, or donations
- Requests for ID cards, bank cards, or verification codes
- Claims of being police without verifiable identification
- Requests to download unknown apps, enable screen sharing, or click unfamiliar links
Safety Command:
When encountering suspicious situations, run:
CODEBLOCK1
Testing
Minimum Test Coverage:
Run the basic test suite:
CODEBLOCK2
Test Coverage Areas:
- - Case creation
- Case listing
- Clue addition
- Notice generation
- Progress tracking
- Safety reminders
Skill Metadata
| Attribute | Value |
|---|
| Name | Looking for Someone |
| Slug |
looking-for-someone |
|
Version | 1.0.2 |
|
Category | Utility / Safety |
|
Tags | missing-person, safety, local-assistance, case-management |
Related Skills
- - emergency-contacts - Emergency contact management
- safety-check - Personal safety checklists
- document-organizer - Document organization and management
Important: This skill is a local organization and guidance tool. It does not replace official channels, police reports, or professional search services. Always prioritize contacting authorities in missing person situations.
寻人技能
概述
本技能帮助用户在本地区组织和管理失踪人员案件。它提供结构化的案件创建、线索管理、寻人启事生成和搜索指导工作流程,同时强调安全、隐私以及官方渠道的合理使用。
执行原则
- - 首先确认目标:识别用户是需要创建案件、添加线索、生成寻人启事、跟踪进展还是获取搜索建议。
- 优先推荐官方渠道:始终建议联系相关部门,特别是涉及未成年人、老年人、心理健康问题、自残风险或长期失踪的高风险场景。
- 透明说明能力范围:不得声称可访问官方数据库、监控系统或实时社交媒体搜索。
- 避免不切实际的声明:不得承诺未实现的功能,如加密、图像比对或身份验证。
- 谨慎处理敏感信息:默认谨慎处理寻人启事中的地址、身份证号、银行卡号及其他敏感数据。
可用功能
- - 案件管理:创建和查看本地失踪人员案件
- 线索管理:添加线索并提供基础分析
- 寻人启事生成:为不同平台生成寻人启事
- 进展跟踪:查看案件进展及下一步建议
- 搜索指导:提供结构化的搜索建议
- 安全提醒:输出防诈骗和安全提醒
操作方法
主要命令行界面
bash
创建新案件
node scripts/cli.js create <案件JSON>
列出所有案件
node scripts/cli.js list
查看案件进展
node scripts/cli.js progress <案件ID>
为案件添加线索
node scripts/cli.js clue <案件ID> <线索内容>
生成寻人启事
node scripts/cli.js notice <案件ID> [general|wechat|weibo|douyin|official]
获取搜索指导
node scripts/cli.js guide
显示安全提醒
node scripts/cli.js reminders
案件创建输入指南
案件创建必填字段:
- - name - 失踪人员全名
- age - 失踪时年龄
- gender - 性别
- lastSeenDate - 最后出现日期(YYYY-MM-DD格式)
- lastSeenLocation - 最后出现地点
可选字段:
- - phone - 联系电话
- birthDate - 出生日期
- idNumber - 身份证号码(谨慎使用)
- height - 身高(厘米)
- clothing - 失踪时衣着描述
- distinguishingFeatures - 显著身体特征
- circumstances - 失踪情况
- possibleDestinations - 可能前往的地点
- familyContacts - 家属联系方式
详细字段说明和推荐工作流程请参见 references/fields-and-workflows.md。
数据边界
当前实现:
- - 数据存储:案件保存在本地 ~/.openclaw/skills-data/looking-for-someone/
- 存储格式:当前版本使用本地JSON文件存储案件
- 限制:未实现字段级加密、图像识别、照片比对、在线爬取或身份验证
透明度要求:
- - 在所有输出中明确说明这些限制
- 提醒用户通过警方和官方渠道核实信息
- 避免夸大能力
隐私和安全边界详见 references/privacy-and-boundaries.md。
输出呈现要求
- - 恰当呈现建议:将建议表述为本地组织结果或基于规则的建议
- 避免事实性断言:不得将线索分析呈现为事实判断
- 优先处理高风险案件:对于高风险情况,优先推荐联系警方和官方渠道
- 处理不完整数据:在数据不完整时,引导用户在生成寻人启事前补充关键信息
安全要求
需要立即警告的风险场景:
- - 要求付费换取信息
- 要求预先转账、押金或捐款
- 要求提供身份证、银行卡或验证码
- 自称是警方但无法提供可验证身份
- 要求下载未知应用、开启屏幕共享或点击陌生链接
安全命令:
遇到可疑情况时,运行:
bash
node scripts/cli.js reminders
测试
最低测试覆盖:
运行基础测试套件:
bash
node test.js
测试覆盖范围:
- - 案件创建
- 案件列表
- 线索添加
- 寻人启事生成
- 进展跟踪
- 安全提醒
技能元数据
looking-for-someone |
|
版本 | 1.0.2 |
|
类别 | 工具/安全 |
|
标签 | 失踪人员, 安全, 本地协助, 案件管理 |
相关技能
- - emergency-contacts - 紧急联系人管理
- safety-check - 个人安全检查清单
- document-organizer - 文档组织与管理
重要提示:本技能是一个本地组织和指导工具。它不能替代官方渠道、警方报案或专业搜索服务。在失踪人员情况下,始终优先联系相关部门。