sf-metadata by jaganpro/sf-skills
npx skills add https://github.com/jaganpro/sf-skills --skill sf-metadata当用户需要元数据定义或组织元数据发现时使用此技能:自定义对象、字段、验证规则、记录类型、页面布局、权限集,或使用 sf CLI 进行模式检查。
当工作涉及以下内容时,使用 sf-metadata:
.object-meta.xml、.field-meta.xml、.profile-meta.xml 及相关元数据文件当用户进行以下操作时,请委托给其他技能:
广告位招租
在这里展示您的产品或服务
触达数万 AI 开发者,精准高效
询问或推断:
除非用户明确选择退出,否则假定新的自定义对象或字段需要权限集跟进。
| 模式 | 使用场景 |
|---|---|
| 生成 | 用户需要新的或更新的元数据 XML |
| 查询 | 用户需要进行对象 / 字段 / 元数据发现 |
对于生成,使用以下目录下的资源:
assets/objects/assets/fields/assets/permission-sets/assets/profiles/assets/record-types/assets/validation-rules/assets/layouts/对于查询,优先使用 sf 元数据和 sobject describe 命令。
检查:
当创建新的自定义字段或对象时:
fieldPermissions当用户需要推出元数据时,使用 sf-deploy。
fieldPermissions,而不是将 FLS 留作手动事后处理完成时,按此顺序报告:
建议格式:
Metadata task: <generate / query>
Items: <objects, fields, rules, layouts, permsets>
Files: <paths>
Notes: <naming, field types, security, dependencies>
Next step: <deploy, assign permset, or verify in Setup>
| 需求 | 委托给 | 原因 |
|---|---|---|
| 部署元数据 | sf-deploy | 推出和验证 |
| 在新模式上构建 Flow | sf-flow | 声明式自动化 |
| 在新模式上构建 Apex | sf-apex | 针对元数据编码 |
| 创建后分析权限访问 | sf-permissions | 访问审计 |
| 部署后植入数据 | sf-data | 测试数据创建 |
| 分数 | 含义 |
|---|---|
| 108+ | 强大的生产就绪元数据 |
| 96–107 | 良好的元数据,有少量待审查项 |
| 84–95 | 可接受,但需仔细验证 |
| < 84 | 阻止部署,直至修正 |
每周安装数
292
仓库
GitHub 星标数
223
首次出现
2026年1月22日
安全审计
安装于
codex282
cursor281
opencode280
gemini-cli279
github-copilot276
amp273
Use this skill when the user needs metadata definition or org metadata discovery : custom objects, fields, validation rules, record types, page layouts, permission sets, or schema inspection with sf CLI.
Use sf-metadata when the work involves:
.object-meta.xml, .field-meta.xml, .profile-meta.xml, and related metadata filesDelegate elsewhere when the user is:
Ask for or infer:
Unless the user explicitly opts out, assume new custom objects or fields need permission-set follow-up.
| Mode | Use when |
|---|---|
| generation | the user wants new or updated metadata XML |
| querying | the user needs object / field / metadata discovery |
For generation, use the assets under:
assets/objects/assets/fields/assets/permission-sets/assets/profiles/assets/record-types/assets/validation-rules/assets/layouts/For querying, prefer sf metadata and sobject describe commands.
Check:
When new custom fields or objects are created:
fieldPermissions for eligible custom fieldsUse sf-deploy when the user needs the metadata rolled out.
fieldPermissions for eligible custom fields instead of leaving FLS as a manual afterthoughtWhen finishing, report in this order:
Suggested shape:
Metadata task: <generate / query>
Items: <objects, fields, rules, layouts, permsets>
Files: <paths>
Notes: <naming, field types, security, dependencies>
Next step: <deploy, assign permset, or verify in Setup>
| Need | Delegate to | Reason |
|---|---|---|
| deploy metadata | sf-deploy | rollout and validation |
| build Flows on new schema | sf-flow | declarative automation |
| build Apex on new schema | sf-apex | code against metadata |
| analyze permission access after creation | sf-permissions | access auditing |
| seed data after deploy | sf-data | test data creation |
| Score | Meaning |
|---|---|
| 108+ | strong production-ready metadata |
| 96–107 | good metadata with minor review items |
| 84–95 | acceptable but validate carefully |
| < 84 | block deployment until corrected |
Weekly Installs
292
Repository
GitHub Stars
223
First Seen
Jan 22, 2026
Security Audits
Gen Agent Trust HubPassSocketPassSnykPass
Installed on
codex282
cursor281
opencode280
gemini-cli279
github-copilot276
amp273
agent-browser 浏览器自动化工具 - Vercel Labs 命令行网页操作与测试
140,500 周安装