marceloarbore/knowledge-one-view-cli
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Commit pre-revisao de simplificação e elegancia do superpowers

Browse Source
This commit is contained in:
Marcelo Arbore
2026-05-05 11:51:57 -03:00
parent d0918936a3
commit 5ea33e353e
2 changed files with 14 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
SKILL.md
View File

@@ -142,6 +142,10 @@ Use `--sql` only when `--query` cannot express the ask cleanly.
## Data-Specific Rules
- For manager or hierarchy asks, start with [references/initial-context-catalog.md](references/initial-context-catalog.md) before touching the CLI catalog.
- For any effort/hour allocation ask, default to 100% of recorded hours. Include customer-related work, non-customer/internal work, and Time Off unless the user explicitly asks to exclude one of those categories.
- For `DV - SE Team` effort/hour reads, use `"Effort"."# Hours"` as the default total-hours measure. Use `"Effort"."# Hours (Excl. Time Off)"` only when the user explicitly asks to exclude Time Off or when a specific built-in view forces that metric; if forced, disclose the limitation.
- For `Knowledge DV - Hours - V2` or other XSA hour reads, prefer the available total-hours measure that includes Time Off. If only an excluding-Time-Off alias such as `hoursExcludingTimeOff` is available, probe or use `--sql` to validate a total-hours field before falling back.
- Do not filter hours to only customer, only non-customer, only opportunity-linked, only internal, or only Time Off unless the user explicitly requests that subset.
- For generic opportunity and pipeline asks, prefer `opportunities-default`.
- For close-date asks, prefer `opportunities-close-date`, `opportunities-close-month`, or `opportunities-close-window`.
- For fiscal-quarter asks, prefer `--quarter` with `FY26-Q4`, `Q4 FY26`, or `current-quarter`.
@@ -165,6 +169,9 @@ Use `--sql` only when `--query` cannot express the ask cleanly.
- Use `--owner-email` for direct territory-owner filters and `--owner-manager-email` for owner-hierarchy filters on SA Attach workload reads.
- Use `--forecast-type` for natural-language asks such as `forecast`, `upside`, or `won` on SA Attach workload reads.
- Keep opportunity-linked monetary outputs consistent as `bookingValue` and `workloadAmount`.
- For `DV - SE Team` effort/hour reads about activities not related to customers, apply this classification only when the user explicitly asks for non-client, client/non-client splits, internal work, or customer-related filtering. Treat `Unspecified` in all three linkage fields (`Service Request"."SR Number"`, `"Customer"."Customer Name"`, and `"Opportunity"."Opportunity ID"`) as the signal for no customer relationship. Any populated SR, customer, or opportunity means the effort is customer-related.
- For the current validated FY26 my-team pattern, the task types that matched the no-customer signal were `Administration`, `Content Creation`, `Partner Activities`, `Sales Planning`, `Training Delivery`, and `Training/Personal Development - Taken`. `Config`, `Preparation`, and `Travel` were customer-related; `Delivery` and `Follow-up` were mostly customer-related, with small cases that had SR/customer but `Opportunity ID = 'Unspecified'`, so do not classify them as non-customer solely by task type.
- When answering "non-client", "sem cliente", "sem oportunidade", or "atividades internas" effort asks, prefer validating/reporting by the `Unspecified` linkage signal first and only use task type names as a helpful summary of the observed pattern.
- Treat `Knowledge DV - Opportunities - V2` as the normal source for pipeline, opportunity, won, close date, territory, owner, booking, and workload.
- Interpret user wording `vendedor`, `sales rep`, and `lider de vendas` as `territory owner` by default.
- Treat org-wide-capable XSA datasets as org-wide reads in `--scope auto`: `Knowledge DV - Opportunities - V2`, `Knowledge DV - Hours - V2`, `Knowledge DV - Presales Involvement Aux - V1`, and `Knowledge DV - Revn Lines by SE`.
@@ -205,6 +212,7 @@ User-facing answer contract:
- If date windows, weeks, quarters, or "current" wording were interpreted, state the resolved period and the date field being filtered. For commercial SA Attach close-window answers, say that the window filters `Revenue Line Close Date`.
- If user wording required role interpretation, state it briefly, for example `vendedor`/`sales rep`/`lider de vendas` interpreted as `territory owner`, or short Oracle uid normalized to `@oracle.com`.
- If SR, resource, manager, or workload enrichment involved implicit joins, state the join assumption: `opportunityId` is the confirmed linkage; same-resource same-customer SRs without usable `opportunityId` are only fallback candidates; and current-team enrichment can leave unmatched org-wide rows with empty resource fields.
- For hour/effort answers, state whether the reported metric includes Time Off and whether customer and non-customer/internal hours were included. The default is 100% of recorded hours unless an explicit user filter says otherwise.
- Always include API effort and data-shape caveats: `Raw rows pulled from the API: X`; whether the result hit the requested/default limit; any `warnings`; and whether displayed monetary fields use truncated `k` values while `raw` keeps backend-native values.
- Never describe the numbers as "all company", "all Brazil", or "complete pipeline" unless the disclosed `scope`, filters, defaults, and limits actually support that statement.