القائمة
Check content/ mql.yaml query packs for usage of deprecated resources or fields from .lr definitions
يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.
اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.
استنادا إلى تصنيف SOC المهني
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.
npx skills add https://github.com/mondoohq/mql --skill check-querypack-deprecationsيبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.
تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.
عرض SKILL.md
Add staged discovery support to a provider. Use when the user wants to implement staged/phased discovery, break down discovery into stages, add OptionStagedDiscovery support, or optimize a provider's memory usage during discovery. Triggers on requests like "add staged discovery to gcp", "implement staged discovery for aws", "break down discovery for <provider>", or "optimize <provider> discovery".
Use when a provider scan is slow, times out, or trips rate limits (429, throttling, Retry-After), when the same request URL appears many times in a debug log, when an asset's fields look like they cost one API call per scanned asset, or when auditing any provider under providers/ for redundant per-asset API traffic. Applies to aws, azure, gcp, k8s, okta and any other provider, since the resource cache and init dispatch are shared machinery.
Add or change a resource in an existing mql provider — schema, codegen, implementation, tests, and verification against a real target. Use when the user wants to add a resource or fields to a provider (e.g. "add a bind9 resource", "expose the tomcat connectors", "add a resource for named.conf", "model the postfix config"), or when a resource returns null, empty, or wrong values and the cause is the schema rather than the API call.
| name | check-querypack-deprecations |
| description | Check content/ mql.yaml query packs for usage of deprecated resources or fields from .lr definitions |
| disable-model-invocation | true |
| argument-hint | [path-to-mql-yaml (optional, defaults to all)] |
Audit MQL query pack files (*.mql.yaml in content/) against the provider .lr resource definitions to find queries that reference deprecated resources or fields.
Search all providers/*/resources/*.lr files for comments containing "Deprecated" (case-insensitive). For each match, extract:
microsoft.organizations)createdTime)Use Grep to find lines with // Deprecated or / Deprecated in .lr files, then read surrounding context to get the resource/field names.
$ARGUMENTS is provided, check only that file*.mql.yaml files under content/Read each mql.yaml file and examine every mql: block. Check if any deprecated resource name or field appears in the query string. Be thorough:
microsoft.organizations.createdTime, .vpcId, .staticWebsiteHostingcreatedTime on aws.s3.bucket would appear as something accessing .createdTime in a query that operates on s3 bucketsFor each deprecated usage found, report in a markdown table:
If no deprecated usage is found, say so.
Do NOT make any changes to files. This skill is read-only — it only reports findings.