this-name-does-not-match-folder
Frontmatter name doesn't match the folder name; loader should skip.
- License 许可
- Apache-2.0
- 最近更新
- 2026-09-23
- Stars
- ★ 17
- Forks
- 5
01 前言 Front Matter
- name
- this-name-does-not-match-folder
- description
- Frontmatter name doesn't match the folder name; loader should skip.
03 SKILL.md 正文
Wrong Name
The loader should skip skills whose frontmatter name doesn't match
their folder name.
04 同仓库更多 Skills
vendor-privacy-policy-first-pass
Use when the user has a vendor's published privacy policy (URL, PDF, or pasted text) and wants a fast triage assessment to decide whether deeper diligence is warranted. Produces a short structured report covering what the policy says about key data practices (collection, use, sharing, retention, transfers, rights) plus identification of red flags that warrant escalation to deeper review. Explicitly a first pass, not a full privacy assessment, DPA negotiation, or compliance certification.
tabular-review
Use when this matter holds SEVERAL documents and the lawyer wants the same fields compared, extracted, or summarised across them — a due-diligence sweep, a key-terms table, "what is the X in each of these", "compare these contracts". Teaches when to PROACTIVELY offer a grid (so the lawyer discovers the capability), how to map natural language onto start_tabular_review with well-chosen columns, ready-made column templates for common reviews, and — just as important — when NOT to build a grid.
surgical-redline
Use when redlining the other side's contract draft with tracked changes (the apply_redline / preview_redline tools) — for any clause you amend. Teaches how to return each amendment so the tool renders surgical, structure-preserving tracked changes — quote the existing clause and return it with only the necessary words changed (the tool computes the word-level diff and keeps the rest bare), balance one-sided clauses through the right legal mechanism, and preview before you apply.
skill-creator
Use when the user wants to create a new LQ.AI skill, turn a chat into a reusable skill, improve an existing skill, or asks "how do I build a skill that does X." Conducts a focused conversation to elicit what the skill should do, when it should trigger, what inputs and outputs it needs, and what edge cases matter, then produces a complete skill folder ready to save.
ropa-population
Use when building or extending an Article 30 Record of Processing Activities (ROPA) from a source — a privacy notice, a data-processing agreement, an intake questionnaire, or system documentation — using the ROPA tools (propose_processing_activity / propose_system / propose_vendor / propose_transfer, link_processing_activity_to_system, link_vendor_to_activity, add_data_subject_categories, add_data_categories, and the list_* tools). Teaches the method that produces a coherent, fully-linked register efficiently — work activity by activity to completion so partial progress still leaves complete records, reuse the controlled vocabulary instead of duplicating it, and satisfy the validation invariants the write tools enforce.
ropa-maintenance
Use when keeping an existing Article 30 Record of Processing Activities (ROPA) up to date as the business changes — replacing or retiring a tool, system or vendor the company has stopped using (e.g. "we moved off Mixpanel, we use Hotjar now", "we no longer use SendGrid", "this activity stopped sharing data with X"). Teaches the change method using the ROPA change verbs (retire_processing_activity / retire_system / retire_vendor / retire_transfer, unlink_system_from_activity, unlink_vendor_from_activity) together with the propose_* / link_* / list_* tools, so a swap leaves the live register coherent — the new thing linked, the old thing gone from the live register but kept on record for audit. Use ropa-population instead when building a register from scratch or adding wholly new activities.