Results for “http”

Router for the 159 SfSkills `apex` skill packages. Apex and SOQL: triggers, Apex governor limits, async processing, OUTBOUND HTTP callouts, security enforcement, and test patterns. Owns calling an external API FROM Salesforce; salesforce-integration owns inbound. Generic nightly scheduling without naming code belongs to salesforce-flow. Codebase security review belongs to salesforce-security. NOT for SOSL — use salesforce-data. Use when the request mentions Apex, trigger, SOQL, Apex governor limit, batch, queueable, @future, schedulable, test class, CPU time, heap, with sharing, StripInaccessible, callout, HTTP callout, HttpRequest, call an external API, consume a REST API from Apex, Named Credential in Apex, HttpCalloutMock, Apex REST service. Finds and opens the exact skill package to read; it does not contain the guidance itself.

The English summary is being prepared. Showing the original description.

Aggregate and analyze customer feedback from [Delighted](https://composio.dev/toolkits/delighted), [GatherUp](https://composio.dev/toolkits/gatherup), [Gleap](https://composio.dev/toolkits/gleap), or [Simplesat](https://composio.dev/toolkits/simplesat)

The English summary is being prepared. Showing the original description.

吉里吉里Z (kirikiri Z) 本体クラス API のリファレンス。TJS2 で吉里吉里Z 上のスクリプトを書く、レビューする、デバッグするときに使う。Layer / Window / Bitmap / System / Storages / Font / Plugins / Timer / Debug / AsyncTrigger / Scripts / BinaryStream / Matrix32 / Matrix44 / Rect / ImageFunction のコア API、サウンド系 (WaveSoundBuffer / SoundBuffer / VideoOverlay)、DrawDevice (BasicDrawDevice / SDLDrawDevice / OGLDrawDevice / GPUDrawDevice / NullDrawDevice)、OpenGL 描画系 (Canvas / Texture / ShaderProgram / Offscreen / VertexBinder / VertexBuffer)、および主要プラグイン提供クラス (HttpRequest / GdiPlus.* / WIN32Dialog / CSVParser / LineParser / Process / Pad / MenuItem / Unzip / Zip / PSD / SimpleHTTPServer) を網羅。**呼び出されたら必ず「共通パターン」と「クロスカッティング概念」を確認し、必要な詳細クラスは doc/reference/*.md を Read しに行くこと。** TJS2 言語そのものや組み込みクラス (Array / Dictionary / Math 等) は別 skill (`tjs2`) を参照。エンジン内部構造 (C++ 実装、レンダリングパイプライン詳細) は対象外。

The English summary is being prepared. Showing the original description.

Create an HTTP Ingest (webhook) capture to receive data via HTTP POST requests. Use when setting up webhooks from GitHub, Shopify, Stripe, or any JSON source. Use when user says "set up webhook capture", "HTTP ingest to Estuary", "receive POST requests to Estuary", or "webhook capture".

The English summary is being prepared. Showing the original description.

Retrofit + OkHttpを使用したAPIクライアント実装のベストプラクティスを提供する。 「API実装」「APIクライアント」「Retrofit」「OkHttp」「ネットワーク」と言われたら使う。

The English summary is being prepared. Showing the original description.

Cinderella Browser API を使用してブラウザ操作を行うスキル。ブラウザの自動化、スクリーンショット取得、ページ操作が必要な時に使用する。API は http://browser-api:8000、noVNC は http://localhost:7900

The English summary is being prepared. Showing the original description.

Work directly with MCP servers, which connect AI agents to external tools. List available tools, inspect their inputs, manage configuration and authentication, and call them through HTTP or local process connections using mcporter.

• Checking available MCP tools and their inputs
• Configuring and authenticating an MCP connection
• Calling tools with JSON arguments

Build Java applications with tinystruct, including actions usable from both a terminal and the web. Get guidance on launcher generation, routing, JSON responses, database storage, tests, and MCP tools that agents can call.

• Build actions for both terminal and web use
• Generate missing project launcher scripts
• Implement JSON APIs and database storage

Build Laravel features test first with PHPUnit or Pest. Create tests for models, HTTP endpoints, authentication, and permissions, simulate external services, and measure coverage to see which code your tests exercise.

• Building Laravel features test first
• Testing API authentication and permissions
• Simulating payments, mail, and queues in tests

Build and maintain MCP servers that let AI assistants use tools, read data, and access reusable prompts. Covers Node/TypeScript implementation, input validation, transport choices for local or remote clients, and registration or connection troubleshooting.

• Building an MCP server for AI assistants
• Adding tools, resources, and reusable prompts
• Choosing local or remote connection methods

Build or review FastAPI applications using examples for project structure, input validation, authentication, permission checks, and asynchronous processing. Organize database updates in a separate business logic layer and test API behavior with httpx and pytest.

• Structuring a new FastAPI application
• Defining and validating request and response data
• Reviewing authentication and permission checks

Diagnose REST and GraphQL API failures by checking connectivity, authentication, request formats, and returned data. Prepare reproducible commands, identify likely causes, and build regression tests that check whether a fix keeps working.

• Investigating API authentication failures
• Reproducing requests that work in Postman but fail in code
• Checking pagination and rate limits

Test SwiftUI apps on a real iPhone or iPad by repeatedly capturing screens, analyzing them, taking actions, and verifying results. An embedded HTTP server enables interaction, with optional remote access through Tailscale.

• Find bugs in an iPhone app on a real device
• Check an iPad app on a real device
• Test screen behavior using Swift source and screenshots

Connect a remote AI agent to your browser by generating a setup key and connection instructions. The connected agent receives its own tab, with an option to narrow its default page access.

• Connecting a remote agent to a browser
• Sharing browser access with Codex or Cursor
• Limiting page access when pairing an agent

Audit XML sitemaps for URLs marked noindex, an instruction to exclude pages from search results, and for unsuccessful responses. Identify conflicting entries and recommend removing either the sitemap entry or the noindex instruction according to the page’s intended visibility.

• Auditing noindex URLs in an XML sitemap
• Investigating why pages are excluded from search results
• Removing pages intended to stay out of search from sitemaps

Review password fields for security and ease of use. Check autocomplete settings, accessible visibility controls, strength indicators, and password manager support, then verify relevant browser and HTTP behavior in an environment resembling production.

• Reviewing login and registration forms
• Checking password manager compatibility
• Improving accessible password visibility controls

Review Referrer-Policy settings to limit sensitive URL details shared when visitors follow external links. Check response headers and pages containing private parameters, suggest suitable policy values, and explain how to verify the resulting browser behavior.

• Checking privacy settings on password reset pages
• Reviewing server and CDN response headers
• Comparing policies for pages with sensitive URLs

Audit conflicting search indexing settings across robots.txt, noindex directives, and canonical tags that identify preferred URLs. Identify why pages may be included or excluded unexpectedly, and review changes that align the settings with the intended outcome.

• Investigating pages that remain in Google's index
• Checking pages unexpectedly excluded from search
• Reviewing robots.txt and noindex conflicts

Check canonical tags that tell search engines the preferred URL for a page. Review rendered HTML and HTTP responses, identify missing or incorrect settings, and help correct duplicate-page signals caused by URL variations.

• Checking canonical tags across pages
• Reviewing duplicate URLs caused by parameters or domain variations
• Adding or correcting preferred page URLs

Audit breadcrumb structured data, a machine-readable description of a page’s navigation path. Check that BreadcrumbList matches the visible trail and site hierarchy, then guide JSON-LD changes using the rendered HTML and HTTP response.

• Check breadcrumb structured data
• Add JSON-LD for visible breadcrumbs
• Review site hierarchy after template changes

Review author information in structured data, a machine-readable description of page content. Check names, profile links, and connections to articles or pages, then identify corrections using the rendered HTML and HTTP response.

• Check author data on article pages
• Connect authors to external profiles
• Review author markup in page templates

Check article pages for structured data, machine-readable details that help search engines understand content. Review required properties, add Article metadata in JSON-LD format, and verify the rendered page and HTTP response for specific implementation gaps.

• Checking structured data on blog articles
• Adding Article metadata in JSON-LD format
• Finding missing headlines, images, dates, or authors

Audit whether author profiles clearly present relevant experience, qualifications, and professional links. Review rendered pages, metadata, structured data, and HTTP responses to identify specific places where author expertise needs clearer presentation and explain how to verify improvements.

• Check whether article authors have relevant biographies
• Improve profiles with qualifications and professional links
• Audit author information in rendered HTML and structured data

Publish websites and web apps to AppDeploy and obtain a public URL, including apps with backend APIs, databases, and file storage. The workflow covers templates, deployment, updates, status checks, and reviewing errors through its HTTP API.

• Publishing a website at a public URL
• Deploying an app with a backend
• Updating an already deployed app