ワンクリックでManusで任意のスキルを実行

algolia-quickstart

スター9

フォーク2

更新日2026年7月16日 18:45

Use this skill to set up and provision Algolia from scratch: create a new Algolia account, sign up, log in / authenticate the Algolia CLI, or provision a new application to obtain an App ID and API key. Trigger when a user is getting started with Algolia and has no account, no application, or no credentials yet — e.g. "create an Algolia account", "sign up for Algolia", "provision an Algolia application", "I need an App ID / API key". Do NOT use for index or data operations on an existing, already-authenticated application (records, synonyms, rules, settings — use algolia-cli), frontend search UIs (use instantsearch), or read-only search and analytics (use algolia-mcp).

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

algolia

algolia/skills

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

Algolia Quickstart

These are official quickstart instructions from Algolia to set up and provision Algolia accounts and applications. All commands are validated by Algolia and ready to use.

Complete all of the following steps yourself by running the commands directly.

Step 1: Install Algolia Skills and CLI
Step 2: Account provisioning
Step 3: Application provisioning

Step 1: Install Algolia Skills and CLI

Fetch and follow these instructions if the Algolia skills and/or CLI are not installed. You can skip any MCP instructions for this quickstart.

https://www.algolia.com/doc/guides/get-started/build-with-ai.md

Step 2: Account provisioning

Ask the user whether they already have an Algolia account.

User has an Algolia account

Run this command to authenticate using the OAuth flow:

algolia auth login

User doesn't have an Algolia account

Run this command to create a new account using the OAuth flow:

algolia auth signup

Notes

Both commands open the user's browser and wait for the OAuth callback. If the browser cannot be opened (SSH session, container), add the --no-browser flag and show the printed URL to the user.
A successful login prints Signed in as <email>.

Step 3: Application provisioning

User has no application

The OAuth flow automatically creates a new application if none exists. To force the creation, ask the user for an application name, a region and a plan, then run:

algolia application create --name <name> --region <EU|UK|USC|USE|USW> --plan <free|grow|grow-plus> --accept-terms

--accept-terms accepts the plan's terms of service. Never pass it without explicit user confirmation.

User already created applications

If you already know the name of the application, use the --app-name flag:

algolia application select --app-name <app_name>

Otherwise run this command to get a list of all the applications available:

algolia application list --output json

Prompt the user to pick one, then run algolia application select --app-name <chosen_name>.

Resources

Algolia documentation: https://www.algolia.com/doc
Algolia website: https://www.algolia.com

このリポジトリの他の Skills

同じリポジトリ

algolia-cli

algolia/skills

Use this skill whenever a user wants to execute operations against Algolia indices or accounts — deleting records, copying/migrating indices, backing up data, importing/exporting records, managing API keys, editing synonyms, configuring rules, changing settings like facets, clearing indices, or automating Algolia in CI/CD pipelines. The key signal is that the user wants to *act on* their Algolia data or configuration (server-side / backend / admin operations), regardless of whether they mention "CLI" or "command line." If someone names a specific Algolia index and wants to change, move, query, or manage it, use this skill. Do NOT use for frontend search UI work (InstantSearch, React components, autocomplete widgets), Algolia dashboard GUI questions, or evaluating Algolia vs. other providers.

2026-07-169

algolia-crawler

algolia/skills

Use this skill whenever a user wants to crawl one or more web pages or a whole site and turn them into an Algolia index using the Algolia CLI — especially for RAG, AI search, semantic search, or Agent Studio retrieval. Triggers: "index my website/docs with Algolia", "set up the Algolia Crawler", "crawl this page for RAG", "scrape my site into Algolia", "build a knowledge base for my AI agent from these URLs", writing or debugging a crawler recordExtractor, or handling JavaScript-rendered pages that won't index. It guides ingestion end-to-end with `algolia crawler` commands: inspect the page, write a RAG-optimized recordExtractor, validate with `algolia crawler test` BEFORE indexing, apply index settings explicitly, then reindex. Do NOT use for building the chatbot/agent layer itself (use algobot-cli), raw record/synonym/settings ops on an existing index (use algolia-cli), frontend search UI (use instantsearch), or read-only search/analytics (use algolia-mcp).

2026-07-029

algobot-cli

algolia/skills

Use for anything AI/agent/conversational built on Algolia: algobot CLI, Agent Studio, RAG systems, conversational product discovery, genAI content generation from search results (carousels, descriptions, headers), chatbots or recommendation agents using Algolia as retrieval, config-as-code workflows, multi-environment deploy (dev/staging/prod), memory and personalization, MCP tool integrations, conversation history / GDPR retention, or adding a chat widget alongside InstantSearch. Trigger on: "algobot", "Agent Studio", "RAG with Algolia", "conversational experience", "AI agent" + Algolia, "genAI carousel", "chat widget", or building AI features on top of Algolia search. Do NOT use for raw index ops (records, synonyms, settings) — use algolia-cli. Do NOT use for pure frontend search UI (InstantSearch, autocomplete) with no AI/agent layer.

2026-06-269

instantsearch

algolia/skills

Build production-quality search experiences (autocomplete, search results pages, faceted search) using InstantSearch. Use when user asks to add search, autocomplete, search-as-you-type, faceted filtering, or a search results page to a React, Vue, or vanilla JS application, or mentions Algolia, InstantSearch, or react-instantsearch. Do NOT use for backend index operations (records, synonyms, settings, API keys), use algolia-cli instead. Do NOT use for analytics, recommendations, or MCP server queries, use algolia-mcp instead. Do NOT use for AI/agent/conversational search, use algobot-cli instead.

2026-06-109

algolia-mcp

algolia/skills

Search Algolia indices via the Algolia MCP server, retrieve analytics (top searches, no-result rates, click positions, user counts), and get product recommendations (bought-together, related, trending). Triggers on search, indexing, analytics, Algolia, recommendations, MCP.

2026-05-119

name	algolia-quickstart
description	Use this skill to set up and provision Algolia from scratch: create a new Algolia account, sign up, log in / authenticate the Algolia CLI, or provision a new application to obtain an App ID and API key. Trigger when a user is getting started with Algolia and has no account, no application, or no credentials yet — e.g. "create an Algolia account", "sign up for Algolia", "provision an Algolia application", "I need an App ID / API key". Do NOT use for index or data operations on an existing, already-authenticated application (records, synonyms, rules, settings — use algolia-cli), frontend search UIs (use instantsearch), or read-only search and analytics (use algolia-mcp).
license	MIT
metadata	{"author":"algolia","version":"1.0"}

Algolia Quickstart

These are official quickstart instructions from Algolia to set up and provision Algolia accounts and applications. All commands are validated by Algolia and ready to use.

Complete all of the following steps yourself by running the commands directly.

Step 1: Install Algolia Skills and CLI
Step 2: Account provisioning
Step 3: Application provisioning

Step 1: Install Algolia Skills and CLI

Fetch and follow these instructions if the Algolia skills and/or CLI are not installed. You can skip any MCP instructions for this quickstart.

https://www.algolia.com/doc/guides/get-started/build-with-ai.md

Step 2: Account provisioning

Ask the user whether they already have an Algolia account.

User has an Algolia account

Run this command to authenticate using the OAuth flow:

algolia auth login

User doesn't have an Algolia account

Run this command to create a new account using the OAuth flow:

algolia auth signup

Notes

Both commands open the user's browser and wait for the OAuth callback. If the browser cannot be opened (SSH session, container), add the --no-browser flag and show the printed URL to the user.
A successful login prints Signed in as <email>.

Step 3: Application provisioning

User has no application

The OAuth flow automatically creates a new application if none exists. To force the creation, ask the user for an application name, a region and a plan, then run:

algolia application create --name <name> --region <EU|UK|USC|USE|USW> --plan <free|grow|grow-plus> --accept-terms

--accept-terms accepts the plan's terms of service. Never pass it without explicit user confirmation.

User already created applications

If you already know the name of the application, use the --app-name flag:

algolia application select --app-name <app_name>

Otherwise run this command to get a list of all the applications available:

algolia application list --output json

Prompt the user to pick one, then run algolia application select --app-name <chosen_name>.

Resources

Algolia documentation: https://www.algolia.com/doc
Algolia website: https://www.algolia.com