feat(skills): Add 8 operational domain skills (logistics, manufacturing, retail, energy)#290
Open
nocodemf wants to merge 3 commits intoaffaan-m:mainfrom
Open
feat(skills): Add 8 operational domain skills (logistics, manufacturing, retail, energy)#290nocodemf wants to merge 3 commits intoaffaan-m:mainfrom
nocodemf wants to merge 3 commits intoaffaan-m:mainfrom
Conversation
Adds skills covering logistics, manufacturing, retail, and energy operations. Each codifies 15+ years of real industry expertise. Skills: logistics-exception-management, carrier-relationship-management, customs-trade-compliance, inventory-demand-planning, returns-reverse-logistics, production-scheduling, quality-nonconformance, energy-procurement Source: https://github.com/ai-evos/agent-skills License: Apache-2.0 Co-authored-by: Cursor <cursoragent@cursor.com>
Contributor
📝 WalkthroughWalkthroughThis PR adds eight new comprehensive skill documentation files across transportation, compliance, procurement, planning, quality, and returns management domains. Each file defines role context, usage scenarios, core knowledge sections, decision frameworks, edge cases, communication patterns, escalation protocols, and performance indicators following a consistent structure. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~20 minutes Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://cdn.statically.io/img/avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Actionable comments posted: 4
🧹 Nitpick comments (1)
skills/production-scheduling/SKILL.md (1)
5-10: Inconsistent spelling:optimisationvsoptimizationused within the same document.The frontmatter description (Line 5), section heading "Changeover Optimisation" (Line 40), and Additional Resources (Line 213) use the British spelling, while body prose on Lines 48 and 124 uses the American spelling. Pick one variant and apply it consistently throughout.
✏️ Proposed fix (American spelling throughout, to match body prose)
- changeover optimisation, and bottleneck resolution in discrete and batch + changeover optimization, and bottleneck resolution in discrete and batch-### Changeover Optimisation +### Changeover Optimization- Due date compliance trumps changeover optimisation. + Due date compliance trumps changeover optimization.-- For detailed decision frameworks, scheduling algorithms, and optimisation methodologies, see +- For detailed decision frameworks, scheduling algorithms, and optimization methodologies, seeAlso applies to: 40-48, 124-124, 213-213
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@skills/production-scheduling/SKILL.md` around lines 5 - 10, The document uses both British ("optimisation") and American ("optimization") spellings; choose one variant (recommend American to match body prose) and perform a global replace in SKILL.md so all occurrences are consistent—update the frontmatter description, the "Changeover Optimisation" heading, body instances (e.g., the paragraph that references changeovers around the Changeover section) and the Additional Resources entry; ensure you also update any related compound phrases (e.g., "changeover optimisation" => "changeover optimization") and verify headings and TOC entries match exactly.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@skills/returns-reverse-logistics/SKILL.md`:
- Around line 215-217: The skill docs reference three missing files
(decision-frameworks.md, edge-cases.md, communication-templates.md) via relative
links in SKILL.md and seven other skill files; fix by either adding those three
reference files to this PR under the referenced references/ path or by updating
each reference link in the SKILL.md (and the other 7 skill files) to a valid
absolute URL where the documents live; ensure you update all occurrences of
decision-frameworks.md, edge-cases.md, and communication-templates.md so no
cross-reference remains broken and add a note in the PR description if you
choose to defer adding the files to a follow-up PR.
- Around line 1-18: The file SKILL.md for the returns-reverse-logistics skill
violates the lowercase-with-hyphens naming rule; rename SKILL.md to a lowercase
hyphenated name (for example returns-reverse-logistics-skill.md or skill.md) and
update any references to it (e.g., in manifests or imports that use the
filename), ensuring the metadata.name "returns-reverse-logistics" remains
unchanged; apply the same rename pattern to the other seven SKILL.md files so
all eight follow the lowercase-with-hyphens convention.
- Around line 20-217: The file is missing the mandated top-level Markdown
sections "When to Use", "How It Works", and "Examples"; insert three clearly
headed sections into SKILL.md (and the other seven skill files) after the
existing "Role and Context" or before "Core Knowledge" so the document structure
matches the skills guideline; under "When to Use" state the scenarios/triggers
for applying this skill (e.g., returns exceeding threshold, international
returns, recalled items), under "How It Works" outline the step-by-step workflow
and decision points (reference existing subsections like "Returns Policy Logic",
"Inspection and Grading", "Disposition Decision Trees", "Fraud Scoring Model"),
and under "Examples" add 3–5 concrete, short examples or YAML-like use cases
(e.g., Grade A electronics restock flow, hazmat return refusal, influencer bulk
return) to illustrate application.
- Line 13: The SKILL.md files list a broken homepage URL; update the homepage
frontmatter in each of the eight skill files
(skills/returns-reverse-logistics/SKILL.md,
skills/quality-nonconformance/SKILL.md,
skills/logistics-exception-management/SKILL.md,
skills/production-scheduling/SKILL.md,
skills/inventory-demand-planning/SKILL.md, skills/energy-procurement/SKILL.md,
skills/customs-trade-compliance/SKILL.md,
skills/carrier-relationship-management/SKILL.md) by replacing the invalid URL
"https://github.com/evos-ai/evos-capabilities" with the correct repository URL
"https://github.com/ai-evos/agent-skills" in the homepage frontmatter entry.
---
Nitpick comments:
In `@skills/production-scheduling/SKILL.md`:
- Around line 5-10: The document uses both British ("optimisation") and American
("optimization") spellings; choose one variant (recommend American to match body
prose) and perform a global replace in SKILL.md so all occurrences are
consistent—update the frontmatter description, the "Changeover Optimisation"
heading, body instances (e.g., the paragraph that references changeovers around
the Changeover section) and the Additional Resources entry; ensure you also
update any related compound phrases (e.g., "changeover optimisation" =>
"changeover optimization") and verify headings and TOC entries match exactly.
ℹ️ Review info
Configuration used: defaults
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (8)
skills/carrier-relationship-management/SKILL.mdskills/customs-trade-compliance/SKILL.mdskills/energy-procurement/SKILL.mdskills/inventory-demand-planning/SKILL.mdskills/logistics-exception-management/SKILL.mdskills/production-scheduling/SKILL.mdskills/quality-nonconformance/SKILL.mdskills/returns-reverse-logistics/SKILL.md
Comment on lines
1
to
18
| --- | ||
| name: returns-reverse-logistics | ||
| description: > | ||
| Codified expertise for returns authorisation, receipt and inspection, | ||
| disposition decisions, refund processing, fraud detection, and warranty | ||
| claims management. Informed by returns operations managers with 15+ years | ||
| experience. Includes grading frameworks, disposition economics, fraud | ||
| pattern recognition, and vendor recovery processes. Use when handling | ||
| product returns, reverse logistics, refund decisions, return fraud | ||
| detection, or warranty claims. | ||
| license: Apache-2.0 | ||
| version: 1.0.0 | ||
| homepage: https://github.com/evos-ai/evos-capabilities | ||
| metadata: | ||
| author: evos | ||
| clawdbot: | ||
| emoji: "🔄" | ||
| --- |
Contributor
There was a problem hiding this comment.
🛠️ Refactor suggestion | 🟠 Major
SKILL.md filename violates the lowercase-with-hyphens naming convention (applies to all 8 files).
The coding guidelines require lowercase filenames (e.g., python-reviewer.md). All eight new files are named SKILL.md (uppercase). Rename to skill.md or a more descriptive lowercase name such as returns-reverse-logistics-skill.md.
As per coding guidelines: "{agents,skills,commands,hooks}/**/*.{md,json}: Use lowercase with hyphens for file naming."
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@skills/returns-reverse-logistics/SKILL.md` around lines 1 - 18, The file
SKILL.md for the returns-reverse-logistics skill violates the
lowercase-with-hyphens naming rule; rename SKILL.md to a lowercase hyphenated
name (for example returns-reverse-logistics-skill.md or skill.md) and update any
references to it (e.g., in manifests or imports that use the filename), ensuring
the metadata.name "returns-reverse-logistics" remains unchanged; apply the same
rename pattern to the other seven SKILL.md files so all eight follow the
lowercase-with-hyphens convention.
| detection, or warranty claims. | ||
| license: Apache-2.0 | ||
| version: 1.0.0 | ||
| homepage: https://github.com/evos-ai/evos-capabilities |
Contributor
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
# Find all files containing the homepage URL
rg 'homepage:.*evos' --type md --type jsonRepository: affaan-m/everything-claude-code
Length of output: 846
🌐 Web query:
GitHub repository evos-ai/evos-capabilities exists
💡 Result:
The GitHub repository evos-ai/evos-capabilities is not publicly accessible / does not exist at that URL: requesting https://github.com/evos-ai/evos-capabilities returns 404 Not Found. [1]
🌐 Web query:
GitHub repository ai-evos/agent-skills exists
💡 Result:
Yes — the GitHub repository ai-evos/agent-skills exists and is public. [1]
Update homepage URL across all 8 skill files — currently points to non-existent repository.
The homepage URL https://github.com/evos-ai/evos-capabilities does not exist (404 Not Found). The correct repository is https://github.com/ai-evos/agent-skills. Update all 8 skill files: skills/returns-reverse-logistics/SKILL.md, skills/quality-nonconformance/SKILL.md, skills/logistics-exception-management/SKILL.md, skills/production-scheduling/SKILL.md, skills/inventory-demand-planning/SKILL.md, skills/energy-procurement/SKILL.md, skills/customs-trade-compliance/SKILL.md, and skills/carrier-relationship-management/SKILL.md.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@skills/returns-reverse-logistics/SKILL.md` at line 13, The SKILL.md files
list a broken homepage URL; update the homepage frontmatter in each of the eight
skill files (skills/returns-reverse-logistics/SKILL.md,
skills/quality-nonconformance/SKILL.md,
skills/logistics-exception-management/SKILL.md,
skills/production-scheduling/SKILL.md,
skills/inventory-demand-planning/SKILL.md, skills/energy-procurement/SKILL.md,
skills/customs-trade-compliance/SKILL.md,
skills/carrier-relationship-management/SKILL.md) by replacing the invalid URL
"https://github.com/evos-ai/evos-capabilities" with the correct repository URL
"https://github.com/ai-evos/agent-skills" in the homepage frontmatter entry.
Comment on lines
20
to
217
| | Customer account < 30 days old | +10 | New account risk | | ||
| | No-receipt return | +15 | Higher risk of receipt fraud | | ||
| | Item in category with high shrink rate | +5 | Electronics, cosmetics, designer apparel | | ||
|
|
||
| ### Vendor Recovery ROI | ||
|
|
||
| Pursue vendor recovery when: `(Expected credit × probability of collection) > (Labour cost + shipping cost + relationship cost)`. Rules of thumb: | ||
|
|
||
| - Claims > $500: Always pursue. The math works even at 50% collection probability. | ||
| - Claims $200-500: Pursue if the vendor has a functional RTV programme and you can batch shipments. | ||
| - Claims < $200: Batch until threshold is met, or offset against next PO. Do not ship individual units. | ||
| - Overseas vendors: Increase minimum threshold to $1,000. Add 30% to expected processing time. | ||
|
|
||
| ### Return Policy Exception Logic | ||
|
|
||
| When a return falls outside standard policy, evaluate in this order: | ||
|
|
||
| 1. **Is the product defective?** If yes, accept regardless of window or condition. Defective products are the company's problem, not the customer's. | ||
| 2. **Is this a high-value customer?** (Top 10% by LTV) If yes, accept with standard refund. The retention math almost always favours the exception. | ||
| 3. **Is the request reasonable to a neutral observer?** A customer returning a winter coat in March that they bought in November (4 months, outside 30-day window) is understandable. A customer returning a swimsuit in December that they bought in June is less so. | ||
| 4. **What is the disposition outcome?** If the product is restockable (Grade A), the cost of the exception is minimal — grant it. If it's Grade C or worse, the exception costs real margin. | ||
| 5. **Does granting create a precedent risk?** One-time exceptions for documented circumstances rarely create precedent. Publicised exceptions (social media complaints) always do. | ||
|
|
||
| ## Key Edge Cases | ||
|
|
||
| These are situations where standard workflows fail. Brief summaries — see [edge-cases.md](references/edge-cases.md) for full analysis. | ||
|
|
||
| 1. **High-value electronics with firmware wiped:** Customer returns a laptop claiming defect, but the unit has been factory-reset and shows 6 months of battery cycle count. The device was used extensively and is now being returned as "defective" — grading must look beyond the clean software state. | ||
|
|
||
| 2. **Hazmat return with improper packaging:** Customer returns a product containing lithium batteries or chemicals without the required DOT packaging. Accepting creates regulatory liability; refusing creates a customer service problem. The product cannot go back through standard parcel return shipping. | ||
|
|
||
| 3. **Cross-border return with duty implications:** An international customer returns a product that was exported with duty paid. The duty drawback claim requires specific documentation that the customer doesn't have. The return shipping cost may exceed the product value. | ||
|
|
||
| 4. **Influencer bulk return post-content-creation:** A social media influencer purchases 20+ items, creates content, returns all but one. Technically within policy, but the brand value was extracted. Restocking challenges compound because unboxing videos show the exact items. | ||
|
|
||
| 5. **Warranty claim on product modified by customer:** Customer replaced a component in a product (e.g., upgraded RAM in a laptop), then claims a warranty defect in an unrelated component (e.g., screen failure). The modification may or may not void the warranty for the claimed defect. | ||
|
|
||
| 6. **Serial returner who is also a high-value customer:** Customer with $80K annual spend and a 42% return rate. Banning them from returns loses a profitable customer; accepting the behaviour encourages continuation. Requires nuanced segmentation beyond simple return rate. | ||
|
|
||
| 7. **Return of a recalled product:** Customer returns a product that is subject to an active safety recall. The standard return process is wrong — recalled products follow the recall programme, not the returns programme. Mixing them creates liability and reporting errors. | ||
|
|
||
| 8. **Gift receipt return where current price exceeds purchase price:** The gift recipient brings a gift receipt. The item is now selling for $30 more than the gift-giver paid. Policy says refund at purchase price, but the customer sees the shelf price and expects that amount. | ||
|
|
||
| ## Communication Patterns | ||
|
|
||
| ### Tone Calibration | ||
|
|
||
| - **Standard refund confirmation:** Warm, efficient. Lead with the resolution amount and timeline, not the process. | ||
| - **Denial of return:** Empathetic but clear. Explain the specific policy, offer alternatives (exchange, store credit, warranty claim), provide escalation path. Never leave the customer with no options. | ||
| - **Fraud investigation hold:** Neutral, factual. "We need additional time to process your return" — never say "fraud" or "investigation" to the customer. Provide a timeline. Internal communications are where you document the fraud indicators. | ||
| - **Restocking fee explanation:** Transparent. Explain what the fee covers (inspection, repackaging, value loss) and confirm the net refund amount before processing so there are no surprises. | ||
| - **Vendor RTV claim:** Professional, evidence-based. Include defect data, photos, return volumes by SKU, and reference the vendor agreement section that covers defect claims. | ||
|
|
||
| ### Key Templates | ||
|
|
||
| Brief templates below. Full versions with variables in [communication-templates.md](references/communication-templates.md). | ||
|
|
||
| **RMA approval:** Subject: `Return Approved — Order #{order_id}`. Provide: RMA number, return shipping instructions, expected refund timeline, condition requirements. | ||
|
|
||
| **Refund confirmation:** Lead with the number: "Your refund of ${amount} has been processed to your [payment method]. Please allow [X] business days." | ||
|
|
||
| **Fraud hold notice:** "Your return is being reviewed by our processing team. We expect to have an update within [X] business days. We appreciate your patience." | ||
|
|
||
| ## Escalation Protocols | ||
|
|
||
| ### Automatic Escalation Triggers | ||
|
|
||
| | Trigger | Action | Timeline | | ||
| |---|---|---| | ||
| | Return value > $5,000 (single item) | Supervisor approval required before refund | Before processing | | ||
| | Fraud score ≥ 80 | Hold refund, route to fraud review team | Immediately | | ||
| | Customer has filed chargeback simultaneously | Halt return processing, coordinate with payments team | Within 1 hour | | ||
| | Product identified as recalled | Route to recall coordinator, do not process as standard return | Immediately | | ||
| | Vendor defect rate exceeds 5% for SKU | Notify merchandise and vendor management | Within 24 hours | | ||
| | Third policy exception request from same customer in 12 months | Manager review before granting | Before processing | | ||
| | Suspected counterfeit in return stream | Pull from processing, photograph, notify LP and brand protection | Immediately | | ||
| | Return involves regulated product (pharma, hazmat, medical device) | Route to compliance team | Immediately | | ||
|
|
||
| ### Escalation Chain | ||
|
|
||
| Level 1 (Returns Associate) → Level 2 (Team Lead, 2 hours) → Level 3 (Returns Manager, 8 hours) → Level 4 (Director of Operations, 24 hours) → Level 5 (VP, 48+ hours or any single-item return > $25K) | ||
|
|
||
| ## Performance Indicators | ||
|
|
||
| | Metric | Target | Red Flag | | ||
| |---|---|---| | ||
| | Return processing time (receipt to refund) | < 48 hours | > 96 hours | | ||
| | Inspection accuracy (grade agreement on audit) | > 95% | < 88% | | ||
| | Restock rate (% of returns restocked as new/open box) | > 45% | < 30% | | ||
| | Fraud detection rate (confirmed fraud caught) | > 80% | < 60% | | ||
| | False positive rate (legitimate returns flagged) | < 3% | > 8% | | ||
| | Vendor recovery rate ($ recovered / $ eligible) | > 70% | < 45% | | ||
| | Customer satisfaction (post-return CSAT) | > 4.2/5.0 | < 3.5/5.0 | | ||
| | Cost per return processed | < $8.00 | > $15.00 | | ||
|
|
||
| ## Additional Resources | ||
|
|
||
| - For detailed disposition trees, fraud scoring, vendor recovery frameworks, and grading standards, see [decision-frameworks.md](references/decision-frameworks.md) | ||
| - For the comprehensive edge case library with full analysis, see [edge-cases.md](references/edge-cases.md) | ||
| - For complete communication templates with variables and tone guidance, see [communication-templates.md](references/communication-templates.md) |
Contributor
There was a problem hiding this comment.
🛠️ Refactor suggestion | 🟠 Major
Missing required sections: When to Use, How It Works, and Examples (applies to all 8 files).
The coding guidelines and retrieved learnings specify that skill documents must contain these three named sections. None of the eight new files include them. The existing content (description frontmatter, Role and Context, Decision Frameworks, Key Edge Cases) partially covers the intent but does not satisfy the structural requirement.
Consider restructuring each skill to add:
+## When to Use
+<!-- surface the "Use when…" prose already in the frontmatter description here -->
+## How It Works
+<!-- brief overview of the skill's reasoning process -->
+## Examples
+<!-- one or two concrete worked examples showing the skill in action -->As per coding guidelines: "skills/**/*.md: Skills should be formatted as Markdown with clear sections for When to Use, How It Works, and Examples." Based on learnings: "Applies to skills/**/*.md: Skills should be formatted as Markdown with clear sections for When to Use, How It Works, and Examples."
🧰 Tools
🪛 LanguageTool
[style] ~49-~49: ‘almost never’ might be wordy. Consider a shorter alternative.
Context: .... Cosmetics and personal care items are almost never restockable once opened due to health r...
(EN_WORDINESS_PREMIUM_ALMOST_NEVER)
[style] ~57-~57: The double modal “Requires dedicated” is nonstandard (only accepted in certain dialects). Consider “to be dedicated”.
Context: ...r tools, and small appliances. Requires dedicated refurb station, spare parts inventory, ...
(NEEDS_FIXED)
[style] ~116-~116: Did you mean ‘different from’? ‘Different than’ is often considered colloquial style.
Context: ...ignal | | Return from address different than shipping address | +10 | Gift returns e...
(DIFFERENT_THAN)
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@skills/returns-reverse-logistics/SKILL.md` around lines 20 - 217, The file is
missing the mandated top-level Markdown sections "When to Use", "How It Works",
and "Examples"; insert three clearly headed sections into SKILL.md (and the
other seven skill files) after the existing "Role and Context" or before "Core
Knowledge" so the document structure matches the skills guideline; under "When
to Use" state the scenarios/triggers for applying this skill (e.g., returns
exceeding threshold, international returns, recalled items), under "How It
Works" outline the step-by-step workflow and decision points (reference existing
subsections like "Returns Policy Logic", "Inspection and Grading", "Disposition
Decision Trees", "Fraud Scoring Model"), and under "Examples" add 3–5 concrete,
short examples or YAML-like use cases (e.g., Grade A electronics restock flow,
hazmat return refusal, influencer bulk return) to illustrate application.
Comment on lines
+215
to
+217
| - For detailed disposition trees, fraud scoring, vendor recovery frameworks, and grading standards, see [decision-frameworks.md](references/decision-frameworks.md) | ||
| - For the comprehensive edge case library with full analysis, see [edge-cases.md](references/edge-cases.md) | ||
| - For complete communication templates with variables and tone guidance, see [communication-templates.md](references/communication-templates.md) |
Contributor
There was a problem hiding this comment.
Linked reference files (decision-frameworks.md, edge-cases.md, communication-templates.md) are not included in this PR (applies to all 8 files).
Every skill document links to three relative paths (references/decision-frameworks.md, references/edge-cases.md, references/communication-templates.md). None of these files are part of this PR, so all cross-references are currently broken. If they live in an external repository, consider replacing the relative links with absolute URLs, or include them in a follow-up PR and note the dependency.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@skills/returns-reverse-logistics/SKILL.md` around lines 215 - 217, The skill
docs reference three missing files (decision-frameworks.md, edge-cases.md,
communication-templates.md) via relative links in SKILL.md and seven other skill
files; fix by either adding those three reference files to this PR under the
referenced references/ path or by updating each reference link in the SKILL.md
(and the other 7 skill files) to a valid absolute URL where the documents live;
ensure you update all occurrences of decision-frameworks.md, edge-cases.md, and
communication-templates.md so no cross-reference remains broken and add a note
in the PR description if you choose to defer adding the files to a follow-up PR.
Adds eval-verified skills for logistics, manufacturing, retail, and energy operations. Each codifies 15+ years of real industry expertise. Source: https://github.com/ai-evos/agent-skills License: Apache-2.0 Co-authored-by: Cursor <cursoragent@cursor.com>
nocodemf
changed the title
Contributor
There was a problem hiding this comment.
Actionable comments posted: 13
♻️ Duplicate comments (1)
skills/returns-reverse-logistics/SKILL.md (1)
1-27: Previously raised structural issues still apply (filename + required section headings).No new information beyond prior feedback; existing comments on naming convention and required
When to Use/How It Works/Examplessections remain valid.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@skills/returns-reverse-logistics/SKILL.md` around lines 1 - 27, The SKILL.md file (skill name "returns-reverse-logistics") is missing required structural headings and may not follow naming conventions; update the frontmatter name to follow the project's naming convention and add the required sections "When to Use", "How It Works", and "Examples" under the "# Returns & Reverse Logistics" content so the document meets template expectations—ensure each new section contains a short descriptive paragraph and at least one practical example or usage scenario, and keep section titles exactly "When to Use", "How It Works", and "Examples" to match validation rules.
🧹 Nitpick comments (1)
skills/returns-reverse-logistics/SKILL.md (1)
117-117: Prefer “different from” in policy table text.Small wording polish: “different from” reads more standard than “different than” here.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@skills/returns-reverse-logistics/SKILL.md` at line 117, Update the policy table cell text that currently reads "Return from address different than shipping address" to use the preferred phrasing "Return from address different from shipping address" (edit the table row in SKILL.md where that exact phrase appears).
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@skills/carrier-relationship-management/SKILL.md`:
- Line 1: Rename the file currently named SKILL.md to follow the repository
naming convention (use all lowercase with hyphens); for this skill rename
SKILL.md to carrier-relationship-management.md, and update any references to
SKILL.md elsewhere (indexes, manifests, README links, or import/require
statements) to point to the new lowercase-hyphen filename so references remain
valid.
- Around line 20-27: Add the three required top-level Markdown sections to this
skill document: insert explicit headings "When to Use", "How It Works", and
"Examples" below the existing "Core Knowledge" content; under "When to Use"
describe scenarios and triggers for applying this
carrier-relationship-management skill, under "How It Works" document the
step-by-step process and systems involved (TMS, rate platforms, onboarding,
FMCSA checks, scorecards), and under "Examples" provide 2–3 concrete use cases
or sample workflows (e.g., onboarding a new carrier, running an RFP,
reallocating during tight capacity) so the file conforms to the skills/**/*.md
guideline.
In `@skills/customs-trade-compliance/SKILL.md`:
- Around line 21-27: The SKILL.md for the Customs & Trade Compliance skill is
missing the required "When to Use", "How It Works", and "Examples" sections;
update SKILL.md (the document that currently contains "Role and Context" and
"Core Knowledge") by adding three explicit Markdown headings "## When to Use",
"## How It Works", and "## Examples" after the existing content (place them
where they logically fit, e.g., following "Core Knowledge"), and populate each
with concise guidance: criteria for invoking the skill under "When to Use", a
brief operational overview or workflow under "How It Works", and at least one
concrete usage example under "Examples".
- Line 1: Rename the file skills/customs-trade-compliance/SKILL.md to use
lowercase with hyphens to match the repository convention (e.g.,
skills/customs-trade-compliance/customs-trade-compliance.md or a more specific
hyphenated name as appropriate); update any references or imports that point to
SKILL.md (search for "SKILL.md" in the codebase) so they use the new
lowercase-hyphen filename to avoid broken links.
In `@skills/energy-procurement/SKILL.md`:
- Line 1: The file named SKILL.md must be renamed to follow the repository
convention of lowercase with hyphens; locate SKILL.md and rename it to a
lowercase, hyphenated name that reflects the skill (for example
energy-procurement.md or energy-procurement-skill.md), update any references to
SKILL.md in docs or manifests to the new filename, and ensure the commit
includes only the rename (or a git mv) so history is preserved.
- Around line 21-27: The SKILL.md is missing the mandatory Markdown sections;
add explicit top-level headings "When to Use", "How It Works", and "Examples"
(placed after the existing "Core Knowledge" heading or where appropriate in the
flow) and populate each with concise guidance: "When to Use" should state
scenarios and decision criteria for this skill, "How It Works" should summarize
the procurement lifecycle and key systems/processes (tariff analysis, RFPs,
meter/market data, contract negotiation, demand charge management, PPAs), and
"Examples" should include 2–3 concrete use cases or workflows (e.g., RFP for a
new supplier, demand-charge mitigation during peak season, PPA evaluation) to
illustrate application; keep headings exact so automated checks pick them up.
In `@skills/inventory-demand-planning/SKILL.md`:
- Around line 21-27: The SKILL.md for Inventory Demand Planning is missing the
required sections; add explicit Markdown headings "When to Use", "How It Works",
and "Examples" below the existing "Core Knowledge" section; under "When to Use"
list concise scenarios and constraints where this skill applies (e.g.,
multi-location retailer, SKU count, systems present), under "How It Works"
describe the end-to-end process (data inputs: POS, ERP, WMS, demand planning
suite; forecasting, safety stock, order generation, approvals, PO execution),
and under "Examples" provide 2–3 short concrete examples (e.g., seasonal
promotion planning, DC replenishment for a new SKU, clearance markdown-driven
demand adjustments) so the file conforms to the skills/*.md guideline.
- Line 1: Rename the file skills/inventory-demand-planning/SKILL.md to a
lowercase-hyphen name (e.g.,
skills/inventory-demand-planning/inventory-demand-planning.md) to follow the
repository convention; update any references or links that point to SKILL.md to
the new filename and commit the rename so CI and docs resolve correctly.
In `@skills/production-scheduling/SKILL.md`:
- Line 125: The document mixes British and American spelling (e.g., "optimised"
vs "optimized"); choose one variant (pick either "optimised"/"optimisation" or
"optimized"/"optimization") and replace all occurrences consistently—for
example, change the phrase in the "Validate against due dates" line (and the
occurrence around lines referencing "optimised sequence"/"optimisation") and the
other instance noted (line 214) so the entire SKILL.md uses the same spelling
variant throughout.
- Line 1: Rename the markdown asset currently named SKILL.md to a lowercase
hyphenated filename (production-scheduling.md) to comply with the repository
naming rule; update any references or links that point to SKILL.md (README,
index files, or other markdown docs) to the new production-scheduling.md name
and ensure commits/PR title reflect the rename so CI and docs consumers pick up
the change.
- Around line 21-27: The SKILL.md is missing the required top-level sections;
add three top-level Markdown sections titled "When to Use", "How It Works", and
"Examples" (placed after the existing "Core Knowledge" or immediately under the
header block) and populate them with concise guidance: "When to Use" describing
scenarios and prerequisites for applying Production Scheduling, "How It Works"
explaining the minutes-by-minute sequencing, inputs (work orders, routings,
BOMs), constraints (capacity, changeovers, labour, quality), and interactions
with ERP/MES/CMMS, and "Examples" showing 2–3 practical use cases (e.g.,
resolving a bottleneck, scheduling a mixed-model line, handling a late order).
Ensure headings use Markdown syntax and follow the project's skills/**/*.md
formatting guidelines.
In `@skills/quality-nonconformance/SKILL.md`:
- Line 1: Rename the file currently named "SKILL.md" to follow the repo markdown
naming convention: use lowercase with hyphens; for this skill use
"quality-nonconformance.md" (or another lowercase-hyphen name that reflects the
skill). Update any references to "SKILL.md" within the repo (docs, index, or
manifest) to the new filename so links and imports continue to work.
- Around line 21-27: The SKILL.md is missing required top-level sections; add
explicit Markdown headings "When to Use", "How It Works", and "Examples" as
top-level (##) sections in skills/quality-nonconformance/SKILL.md, placing them
after the existing "Role and Context" and before or around "Core Knowledge" so
the document follows the skills/**/*.md guideline and clearly separates usage
guidance, operational explanation, and concrete examples.
---
Duplicate comments:
In `@skills/returns-reverse-logistics/SKILL.md`:
- Around line 1-27: The SKILL.md file (skill name "returns-reverse-logistics")
is missing required structural headings and may not follow naming conventions;
update the frontmatter name to follow the project's naming convention and add
the required sections "When to Use", "How It Works", and "Examples" under the "#
Returns & Reverse Logistics" content so the document meets template
expectations—ensure each new section contains a short descriptive paragraph and
at least one practical example or usage scenario, and keep section titles
exactly "When to Use", "How It Works", and "Examples" to match validation rules.
---
Nitpick comments:
In `@skills/returns-reverse-logistics/SKILL.md`:
- Line 117: Update the policy table cell text that currently reads "Return from
address different than shipping address" to use the preferred phrasing "Return
from address different from shipping address" (edit the table row in SKILL.md
where that exact phrase appears).
ℹ️ Review info
Configuration used: defaults
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (8)
skills/carrier-relationship-management/SKILL.mdskills/customs-trade-compliance/SKILL.mdskills/energy-procurement/SKILL.mdskills/inventory-demand-planning/SKILL.mdskills/logistics-exception-management/SKILL.mdskills/production-scheduling/SKILL.mdskills/quality-nonconformance/SKILL.mdskills/returns-reverse-logistics/SKILL.md
🚧 Files skipped from review as they are similar to previous changes (1)
- skills/logistics-exception-management/SKILL.md
| @@ -0,0 +1,190 @@ | |||
| --- | |||
Contributor
There was a problem hiding this comment.
🛠️ Refactor suggestion | 🟠 Major
Filename does not follow lowercase-hyphen convention.
Please rename SKILL.md to match repository file naming rules.
As per coding guidelines: "{agents,skills,commands,hooks}/**/*.{md,json}: Use lowercase with hyphens for file naming (e.g., python-reviewer.md, tdd-workflow.md)."
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@skills/carrier-relationship-management/SKILL.md` at line 1, Rename the file
currently named SKILL.md to follow the repository naming convention (use all
lowercase with hyphens); for this skill rename SKILL.md to
carrier-relationship-management.md, and update any references to SKILL.md
elsewhere (indexes, manifests, README links, or import/require statements) to
point to the new lowercase-hyphen filename so references remain valid.
skills/carrier-relationship-management/carrier-relationship-management.md
Show resolved
Hide resolved
| @@ -0,0 +1,241 @@ | |||
| --- | |||
Contributor
There was a problem hiding this comment.
🛠️ Refactor suggestion | 🟠 Major
Rename SKILL.md to lowercase-hyphen format.
This path does not conform to the markdown filename convention for skills/**.
As per coding guidelines: "{agents,skills,commands,hooks}/**/*.{md,json}: Use lowercase with hyphens for file naming (e.g., python-reviewer.md, tdd-workflow.md)."
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@skills/customs-trade-compliance/SKILL.md` at line 1, Rename the file
skills/customs-trade-compliance/SKILL.md to use lowercase with hyphens to match
the repository convention (e.g.,
skills/customs-trade-compliance/customs-trade-compliance.md or a more specific
hyphenated name as appropriate); update any references or imports that point to
SKILL.md (search for "SKILL.md" in the codebase) so they use the new
lowercase-hyphen filename to avoid broken links.
| @@ -0,0 +1,205 @@ | |||
| --- | |||
Contributor
There was a problem hiding this comment.
🛠️ Refactor suggestion | 🟠 Major
Filename should be lowercase with hyphens.
SKILL.md should be renamed to follow the repository filename convention.
As per coding guidelines: "{agents,skills,commands,hooks}/**/*.{md,json}: Use lowercase with hyphens for file naming (e.g., python-reviewer.md, tdd-workflow.md)."
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@skills/energy-procurement/SKILL.md` at line 1, The file named SKILL.md must
be renamed to follow the repository convention of lowercase with hyphens; locate
SKILL.md and rename it to a lowercase, hyphenated name that reflects the skill
(for example energy-procurement.md or energy-procurement-skill.md), update any
references to SKILL.md in docs or manifests to the new filename, and ensure the
commit includes only the rename (or a git mv) so history is preserved.
| @@ -0,0 +1,216 @@ | |||
| --- | |||
Contributor
There was a problem hiding this comment.
🛠️ Refactor suggestion | 🟠 Major
Rename SKILL.md to a lowercase hyphenated filename.
The current filename violates the repository naming rule for markdown assets under skills/**.
As per coding guidelines: "{agents,skills,commands,hooks}/**/*.{md,json}: Use lowercase with hyphens for file naming (e.g., python-reviewer.md, tdd-workflow.md)."
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@skills/production-scheduling/SKILL.md` at line 1, Rename the markdown asset
currently named SKILL.md to a lowercase hyphenated filename
(production-scheduling.md) to comply with the repository naming rule; update any
references or links that point to SKILL.md (README, index files, or other
markdown docs) to the new production-scheduling.md name and ensure commits/PR
title reflect the rename so CI and docs consumers pick up the change.
| 2. **Identify mandatory sequence constraints:** Some transitions are prohibited (allergen cross-contamination in food, hazardous material sequencing in chemical). These are hard constraints, not optimisable. | ||
| 3. **Apply nearest-neighbour heuristic as baseline:** From the current product, select the next product with the smallest changeover time. This gives a feasible starting sequence. | ||
| 4. **Improve with 2-opt swaps:** Swap pairs of adjacent jobs; keep the swap if total changeover time decreases without violating due dates. | ||
| 5. **Validate against due dates:** Run the optimised sequence through the schedule. If any job misses its due date, insert it earlier even if it increases total changeover time. Due date compliance trumps changeover optimisation. |
Contributor
There was a problem hiding this comment.
Use one English variant consistently (optimization vs optimisation).
The file currently mixes spellings; standardize to one variant for consistency.
Also applies to: 214-214
🧰 Tools
🪛 LanguageTool
[uncategorized] ~125-~125: Do not mix variants of the same word (‘optimisation’ and ‘optimization’) within a single text.
Context: .... Due date compliance trumps changeover optimisation. ### Disruption Re-Sequencing When a ...
(EN_WORD_COHERENCY)
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@skills/production-scheduling/SKILL.md` at line 125, The document mixes
British and American spelling (e.g., "optimised" vs "optimized"); choose one
variant (pick either "optimised"/"optimisation" or "optimized"/"optimization")
and replace all occurrences consistently—for example, change the phrase in the
"Validate against due dates" line (and the occurrence around lines referencing
"optimised sequence"/"optimisation") and the other instance noted (line 214) so
the entire SKILL.md uses the same spelling variant throughout.
| @@ -0,0 +1,237 @@ | |||
| --- | |||
Contributor
There was a problem hiding this comment.
🛠️ Refactor suggestion | 🟠 Major
Rename file to comply with lowercase-hyphen naming.
The current SKILL.md name violates the repo naming convention for markdown artifacts.
As per coding guidelines: "{agents,skills,commands,hooks}/**/*.{md,json}: Use lowercase with hyphens for file naming (e.g., python-reviewer.md, tdd-workflow.md)."
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@skills/quality-nonconformance/SKILL.md` at line 1, Rename the file currently
named "SKILL.md" to follow the repo markdown naming convention: use lowercase
with hyphens; for this skill use "quality-nonconformance.md" (or another
lowercase-hyphen name that reflects the skill). Update any references to
"SKILL.md" within the repo (docs, index, or manifest) to the new filename so
links and imports continue to work.
- Rename SKILL.md to <skill-name>.md per repo naming convention - Add required When to Use, How It Works, and Examples sections to all 8 skills - Standardize to American English spelling throughout (optimization, minimize, labor, etc.) - Fix "different than" to "different from" in returns-reverse-logistics Co-authored-by: Cursor <cursoragent@cursor.com>
Contributor
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@skills/logistics-exception-management/logistics-exception-management.md`:
- Around line 12-13: Update the frontmatter key "homepage" which currently
points to "https://github.com/evos-ai/evos-capabilities" so it references the
canonical repository "https://github.com/ai-evos/agent-skills"; locate the
frontmatter block at the top of logistics-exception-management.md and replace
the homepage URL value accordingly.
ℹ️ Review info
Configuration used: defaults
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (8)
skills/carrier-relationship-management/carrier-relationship-management.mdskills/customs-trade-compliance/customs-trade-compliance.mdskills/energy-procurement/energy-procurement.mdskills/inventory-demand-planning/inventory-demand-planning.mdskills/logistics-exception-management/logistics-exception-management.mdskills/production-scheduling/production-scheduling.mdskills/quality-nonconformance/quality-nonconformance.mdskills/returns-reverse-logistics/returns-reverse-logistics.md
Comment on lines
+12
to
+13
| homepage: https://github.com/evos-ai/evos-capabilities | ||
| origin: ECC |
Contributor
There was a problem hiding this comment.
Update frontmatter homepage to the canonical Evos repository URL.
This file points to https://github.com/evos-ai/evos-capabilities, while the PR references https://github.com/ai-evos/agent-skills for the source materials. Please align the URL to avoid dead/outdated links.
🔧 Proposed fix
- homepage: https://github.com/evos-ai/evos-capabilities
+ homepage: https://github.com/ai-evos/agent-skills📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| homepage: https://github.com/evos-ai/evos-capabilities | |
| origin: ECC | |
| homepage: https://github.com/ai-evos/agent-skills | |
| origin: ECC |
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@skills/logistics-exception-management/logistics-exception-management.md`
around lines 12 - 13, Update the frontmatter key "homepage" which currently
points to "https://github.com/evos-ai/evos-capabilities" so it references the
canonical repository "https://github.com/ai-evos/agent-skills"; locate the
frontmatter block at the top of logistics-exception-management.md and replace
the homepage URL value accordingly.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds 8 domain-expert operational skills from Evos, covering logistics, manufacturing, retail, and energy operations.
Skills Added
Each skill codifies 15+ years of real industry expertise. Eval-verified with 93.2% average score across 201 scenarios. Full reference materials and eval suites at https://github.com/ai-evos/agent-skills
License: Apache-2.0
Made with Cursor
Summary by CodeRabbit