'report' 검색 결과

Extract invoice data and generate a formatted PDF summary in a single pipeline.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Generate a formatted XLSX spreadsheet with sales data, currency formatting, and bold headers.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Extract property, owner, legal description, liens, mortgages, easements, and tax status from title search reports.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Extract appraised value, property details, and comparable sales from a property appraisal report into structured JSON.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Extract campaign or business KPIs from report documents — metrics, values, periods, and targets.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Convert external documents — specs, contracts, reports — to markdown for knowledge base ingestion.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Runs the Autoware autonomous-driving stack against CARLA on UE 5.8 over CARLA's native ROS 2 interface — no bridge process. Reports the DDS contract (rt/vehicle/status/* out, rt/control/command/* in), the Autoware-only sensor blueprints, generates the lanelet2 + point-cloud map artifacts Autoware needs instead of an .xodr, and drives the two shipped modes (classical NDT stack, or the camera-only VAD end-to-end model). Use when the user asks to "run Autoware on CARLA", "connect an AV stack", "drive the ego from Autoware", "generate a lanelet2 map", or asks which topics CARLA exchanges with Autoware.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Answers "can CARLA do X here, and is there a vetted procedure for it" before you promise anything, and detects client/server/tree version skew — a support matrix over the whole collection (covered by a skill / works but undocumented / present but untested / broken or removed), an index of the features that are verified BROKEN on 0.10.0 (gbuffers crash the server, map layers do nothing, Landmark.waypoint is None, standalone asset packages are gone), and a probe that reports what this machine's build flags and running server actually offer. Use when the user asks whether CARLA supports something, when a feature has no skill, when a UE4 tutorial's steps do not exist, or before improvising a procedure.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Directly drives a specific vehicle on a running CARLA server — raw VehicleControl (throttle/steer/brake/reverse/hand-brake), Ackermann speed control, vehicle lights, opening/closing doors, and physics-control tuning; ros-info reports the native ROS 2 command topics (vehicle_control_cmd, ackermann_control_cmd) for the hero. Targets the ego by default. Use when the user asks to "drive/steer the car", "accelerate/brake/reverse", "set a target speed", "turn on the headlights/blinkers/brake lights", "open a door", "drive the car from ROS", or "change the vehicle's mass/drag/physics". This is manual control (autopilot off) — for TM-driven traffic use control-traffic.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Runs a single ScenarioRunner Python scenario (or a whole group) against a running CARLA server — FollowLeadingVehicle, ControlLoss, DynamicObjectCrossing, SignalizedJunctionLeftTurn and the rest of srunner/examples — in sync or async mode, with result output, recording and manual/agent control of the ego. Lists what is runnable on the checked-out branch and on the loaded map. Use when the user asks to "run a scenario", "test FollowLeadingVehicle", "list scenarios", "run a CARLA traffic scenario", or reports a scenario that is "not supported".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Runs Scenic probabilistic scenarios against a running CARLA server with the `scenic FILE --simulate --2d` CLI — the carlaChallenge1-10 traffic scenarios shipped by ScenarioRunner (`model srunner.scenic.models.model`) and by Scenic itself (`model scenic.simulators.carla.model`) — bounding the run, sampling scenes headlessly first to tell a map problem from a syntax problem, and restoring the world afterwards. Use when the user asks to "run a Scenic scenario", "run carlaChallenge", "test a .scenic file", "scenic --simulate", or reports a Scenic scenario that rejects every sample or cannot find blueprints.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Downloads CARLA so nothing has to be fetched by hand — an official release package for any published version (resolved live from the GitHub releases, with AdditionalMaps), the rolling nightly Dev build, a shallow source checkout of a branch or tag, or the carlasim/carla Docker image. Reports exactly what was obtained and where, plus the environment variables the other skills read. Use when the user asks to "download CARLA", "get CARLA 0.9.16", "install CARLA", "clone the carla repo", "fetch the latest CARLA", or has no CARLA at all yet.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Listens to a CARLA sensor and either saves its data to files, shows it live in a window, prints a one-shot summary, or (ros-info) reports the native ROS 2 topics, QoS and enabled-for-ROS state so you can echo it from ROS instead. Cameras save as PNG (depth/semantic auto-colourised) and display in a pygame window; lidar saves as .ply and shows as a top-down scatter; IMU/GNSS/radar/collision stream to JSONL or the console. Use when the user asks to "show/view the camera", "display the lidar", "save the sensor data / capture a dataset", or "what is this sensor reading". Select the sensor by id, type, or the actor it's attached to.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Installs the CARLA Python client (the `carla` package) into a chosen interpreter so the other python-api skills work — from a wheel bundled with your release or checkout, from PyPI (`pip install carla==X.Y.Z`), or by putting an older release's .egg on PYTHONPATH. Detects what is already present, picks the source that matches your simulator's version, pins numpy<2, and verifies `import carla` plus the client/server version match. Use when the user asks to "install the CARLA Python API", "pip install carla", "set up the carla python package", or when a skill reports "cannot import carla".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Runs standard-format scenarios through ScenarioRunner — ASAM OpenSCENARIO 1.x (.xosc, via --openscenario, with catalogs and ParameterDeclaration overrides) and OpenSCENARIO 2.0 (.osc, via --openscenario2, the ANTLR/osc2 pipeline). Validates a file against the schema before running, lists the bundled examples, and reports which OSC features ScenarioRunner actually implements. Use when the user asks to "run an xosc", "run an OpenSCENARIO file", "use the OpenSCENARIO standard", "run a .osc / OSC2 scenario", or hands over a scenario file from another tool.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

App Store Connect API 4.5.1 (REST) アプリ配布リファレンス。JWT 認証、API キー作成・失効、 Apps, Builds, Bundle IDs, Bundle ID Capabilities, Certificates, Devices, Provisioning Profiles, Users, User Invitations, Merchant IDs, Pass Type IDs、TestFlight (Beta Groups / Testers)、 Sandbox Testers、App Review, Review Submissions, Customer Reviews, Custom Product Pages, Phased Release、In-App Purchases, Subscriptions, Subscription Groups, App Price Points, Promotional Offers, Win-back Offers, Sales Reports、App Asset Library (screenshots / app previews)、 Webhooks / Webhook Events / Deliveries、Xcode Cloud (Workflows, Build Runs, Artifacts)、 Alternative Distribution (EU マーケットプレイス / Web Distribution)、 Game Center (Achievements, Leaderboards, Challenges)、Analytics / 診断レポート。

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Interact with UI Toolkit (UXML/USS) runtime UI in PlayMode. Use INSTEAD OF uloop-simulate-mouse-ui / uloop-simulate-mouse-input whenever the target UI is UI Toolkit — those tools only reach uGUI and report 'no UI element hit' or silently do nothing on UI Toolkit panels.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Compile the Unity project and report errors/warnings. Use after C# edits or when a full Domain Reload compile is needed.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Run Unity Test Runner and report detailed results. Use for EditMode/PlayMode tests, change verification, or failure diagnosis.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

提案書・調査結果から最終報告書の骨子（章立て・スライド構成・想定アウトプット）を設計するスキル。「報告書骨子を作成して」「章立てを設計して」「レポートの構成を作って」などのリクエスト時に使用。論点構造を報告書の章にマッピングし、プロジェクト種類（技術動向・市場調査・インタビュー中心・DD等）に応じた構成を設計する。

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

最適化結果を非技術者にも伝わる改善提案書にまとめる

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Read a Japanese job posting closely and report what it actually states: base pay separated from fixed overtime allowance, the range converted to an hourly basis, required versus preferred requirements, and the terms left ambiguous. Use when a user wants a 求人票 or job description examined before applying, wants two postings compared on the same basis, or wants questions prepared about pay and working conditions; do not use to judge whether the user will be hired, to infer duties the posting does not state, or to evaluate the employer's reputation.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Prepare for a Japanese job interview by working from the documents already submitted: find where an interviewer will dig in (claims the applicant cannot back up, work described in the first person plural, outcomes with no measure, gaps or overlaps in the employment history, must-have requirements the documents never answer), and turn them into questions to prepare evidence for. Use when a user has an interview scheduled and wants to know what will be asked and what to have ready, or wants to prepare reverse questions from earlier company research; do not use to predict whether they will pass, to write answers containing experience they did not report, or to schedule or contact anyone.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Facilitate DDD domain modeling sessions via EventStorming conversation and DML (Domain Modeling Language). Use whenever the user wants to model a business domain by discovering domain events, commands, aggregates, policies, read models, and bounded contexts through dialogue. Produces incrementally-built DML as the primary artifact, plus a Markdown session report. Also invoke for refining existing DML, mapping out a new feature's domain model, or when the user says "ドメインモデリングしたい", "イベントストーミング", "DDDで整理したい", "DMLを育てたい".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.