Add excel-agent-raycast extension

[BoTigrou]

Description

This is an extension that let the user connect Raycast through an AI provider (OpenAI, Gemini, Anthropic) or Raycast AI to Excel. Through this extension (or using the AI command), Raycast gets agentic capabilities over Excel (example: ask it to do a table; apply a certain style; make formulas, etc).

Screencast

Checklist

• I read the extension guidelines
• I read the documentation about publishing
• I ran npm run build and tested this distribution build in Raycast
• I checked that files in the assets folder are used by the extension itself
• I checked that assets used by the README are placed outside of the metadata folder

[raycastbot]

Congratulations on your new Raycast extension! 🚀

We're currently experiencing a high volume of incoming requests. As a result, the initial review may take up to 10-15 business days.

Once the PR is approved and merged, the extension will be available on our Store.

[greptile-apps]

Greptile Overview

Greptile Summary

This PR adds a new Excel Agent extension that provides AI-powered control of Microsoft Excel via AppleScript. The extension allows users to manipulate spreadsheets using natural language commands through Raycast commands and AI chat integration.

Key Changes:

• New extension with two commands: "Ask Excel" (AI controller) and "Read Excel" (view data)
• AI tool integration for Raycast Chat with the execute-excel-command tool
• Multi-provider support: Raycast AI, OpenAI, Google Gemini, and Anthropic Claude
• Pre-built AppleScript library for common operations (formatting, borders, financial style)
• Context-aware execution that reads sheet name and selection before operations

Issues Found:

• Manual Preferences interface definition in ai-utils.ts should be removed (auto-generated)
• CHANGELOG.md should use {PR_MERGE_DATE} placeholder instead of hardcoded date

Architecture:
The extension uses a hybrid approach: built-in scripts for reliability and AI generation for complex tasks. It properly implements Raycast's tool API for AI chat integration and follows the extension structure guidelines.

Confidence Score: 4/5

• This PR is safe to merge after fixing the two syntax issues (Preferences interface and CHANGELOG date)
• The extension is well-architected with good error handling, proper security considerations (Accessibility permissions), and follows Raycast patterns. The two issues found are minor syntax violations that are easily fixable. The code quality is high with clear separation of concerns, pre-built scripts for reliability, and comprehensive error messages.
• extensions/excel-agent-raycast/src/ai-utils.ts and extensions/excel-agent-raycast/CHANGELOG.md require syntax corrections before merge

Important Files Changed

Filename	Overview
extensions/excel-agent-raycast/package.json	Well-structured package configuration with proper commands, tools, and AI instructions
extensions/excel-agent-raycast/CHANGELOG.md	Comprehensive changelog but uses hardcoded date instead of {PR_MERGE_DATE} placeholder
extensions/excel-agent-raycast/src/ai-utils.ts	Core AI utilities with manual Preferences interface that should be auto-generated
extensions/excel-agent-raycast/src/ask-excel.tsx	Main command view with quick actions and custom commands, imports Preferences type correctly

[greptile-apps]

_{4 files reviewed, 2 comments}

_{Edit Code Review Agent Settings | Greptile}

[greptile-apps]

Manual Preferences interface shouldn't be defined. Preferences are auto-generated in raycast-env.d.ts.

Suggested change

	export interface Preferences {
	aiProvider: "raycast" | "openai" | "gemini" | "claude";
	openaiApiKey?: string;
	geminiApiKey?: string;
	claudeApiKey?: string;
	}
	// Remove this interface - it's auto-generated in raycast-env.d.ts

Context Used: Rule from dashboard - What: Don't manually define Preferences for getPreferenceValues() or commends Argument interfa... (source)

[greptile-apps]

Use {PR_MERGE_DATE} placeholder instead of hardcoded date.

Suggested change

	## [1.0.0] - 2026-01-29
	## [1.0.0] - {PR_MERGE_DATE}

Context Used: Rule from dashboard - What: Changelog entries must use {PR_MERGE_DATE} placeholder in titles, be placed at the top of th... (source)

_{Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!}