@adminforth/agent 2.0.10 → 2.2.0

package/custom/skills/analyze_data/SKILL.md

@@ -1,25 +0,0 @@
-name: analyze_data
-description: Universal skill to analyze AdminForth resource data, summarize trends, and compare distributions from fetched rows.
----
-
-# Involved tools
-
-Always call `get_resource` first if you need to inspect resource structure and column names.
-
-Then you need to select between two main tools for fetching data:
-
-- Load and call `aggregate` tool to fetch data for analytics. This is the main tool for fast server-side aggregations, including filtered data, grouped metrics, and date buckets such as day, week, or month. Always prioritize this way of fetching data for analytics, as it is optimized for performance and reduces the amount of data transferred and processed in-memory.
-
-- Load and call `get_resource_data` tool only when the requested analysis cannot be answered with `aggregate`. When using it, pass `columns` with only the fields required for the calculation so large result sets do not include unrelated row data.
-
-# Instructions
-
-When the user asks for analytics, reports, trends, comparisons, or distributions:
-
-- Fetch the requested data using `aggregate` whenever possible.
-- If it is not possible to get the required aggregates using `aggregate`, fetch the underlying rows with `get_resource_data`.
-- Prefer narrow requests: use filters, sorting, pagination, and date ranges whenever possible.
-- Prefer narrow row payloads: include `columns` when only one or a few fields are needed.
-- If the request is ambiguous, clarify the resource, metric, grouping, or date range before fetching data.
-- Return a short written summary with the key finding and most important numbers.
-- If the user asks for a chart, or if a chart would help and you decide to produce one, invoke the `charts` skill for chart formatting and Vega-Lite requirements.

package/custom/skills/charts/SKILL.md

@@ -1,193 +0,0 @@
-name: charts
-description: Create Vega-Lite chart specs for AdminForth analytics responses. Always use this skill when the user asks for a chart or when a chart would help illustrate the insights from an analytics query.
----
-
-# Instructions
-
-Use Vega-Lite syntax for charts.
-
-Return every chart as valid JSON inside a `vega-lite` fenced code block.
-
-Every chart spec should include:
-
-- `title.text`
-- `title.subtitle`
-- explicit axis titles when axes are used
-- tooltips for the key fields
-
-### Line chart
-
-```vega-lite
-{
-  "$schema": "https://vega.github.io/schema/vega-lite/v5.json",
-  "title": {
-    "text": "Orders by Day",
-    "subtitle": "Daily order count for the selected date range"
-  },
-  "data": {
-    "values": [
-      { "date": "2026-04-01", "orders": 18 },
-      { "date": "2026-04-02", "orders": 25 },
-      { "date": "2026-04-03", "orders": 21 },
-      { "date": "2026-04-04", "orders": 29 }
-    ]
-  },
-  "mark": { "type": "line", "point": true },
-  "encoding": {
-    "x": { "field": "date", "type": "temporal", "title": "Date" },
-    "y": { "field": "orders", "type": "quantitative", "title": "Orders" },
-    "tooltip": [
-      { "field": "date", "type": "temporal", "title": "Date" },
-      { "field": "orders", "type": "quantitative", "title": "Orders" }
-    ]
-  }
-}
-```
-
-### Bar chart
-
-```vega-lite
-{
-  "$schema": "https://vega.github.io/schema/vega-lite/v5.json",
-  "title": {
-    "text": "Revenue by Category",
-    "subtitle": "Top categories in the current filtered dataset"
-  },
-  "data": {
-    "values": [
-      { "category": "Hardware", "revenue": 42000 },
-      { "category": "Software", "revenue": 31500 },
-      { "category": "Services", "revenue": 22750 }
-    ]
-  },
-  "mark": "bar",
-  "encoding": {
-    "x": { "field": "category", "type": "nominal", "title": "Category", "sort": "-y" },
-    "y": { "field": "revenue", "type": "quantitative", "title": "Revenue" },
-    "tooltip": [
-      { "field": "category", "type": "nominal", "title": "Category" },
-      { "field": "revenue", "type": "quantitative", "title": "Revenue" }
-    ]
-  }
-}
-```
-
-### Area chart
-
-```vega-lite
-{
-  "$schema": "https://vega.github.io/schema/vega-lite/v5.json",
-  "title": {
-    "text": "Monthly Signups",
-    "subtitle": "New users accumulated across the last six months"
-  },
-  "data": {
-    "values": [
-      { "month": "2025-11-01", "signups": 120 },
-      { "month": "2025-12-01", "signups": 155 },
-      { "month": "2026-01-01", "signups": 168 },
-      { "month": "2026-02-01", "signups": 190 },
-      { "month": "2026-03-01", "signups": 214 },
-      { "month": "2026-04-01", "signups": 238 }
-    ]
-  },
-  "mark": { "type": "area", "line": true, "point": true },
-  "encoding": {
-    "x": { "field": "month", "type": "temporal", "title": "Month" },
-    "y": { "field": "signups", "type": "quantitative", "title": "Signups" },
-    "tooltip": [
-      { "field": "month", "type": "temporal", "title": "Month" },
-      { "field": "signups", "type": "quantitative", "title": "Signups" }
-    ]
-  }
-}
-```
-
-### Scatter plot
-
-```vega-lite
-{
-  "$schema": "https://vega.github.io/schema/vega-lite/v5.json",
-  "title": {
-    "text": "Ad Spend vs Revenue",
-    "subtitle": "Campaign-level correlation for the selected month"
-  },
-  "data": {
-    "values": [
-      { "campaign": "Search", "spend": 1200, "revenue": 5400 },
-      { "campaign": "Social", "spend": 900, "revenue": 3100 },
-      { "campaign": "Email", "spend": 350, "revenue": 2200 },
-      { "campaign": "Affiliates", "spend": 700, "revenue": 3600 }
-    ]
-  },
-  "mark": { "type": "point", "filled": true, "size": 120 },
-  "encoding": {
-    "x": { "field": "spend", "type": "quantitative", "title": "Ad Spend" },
-    "y": { "field": "revenue", "type": "quantitative", "title": "Revenue" },
-    "tooltip": [
-      { "field": "campaign", "type": "nominal", "title": "Campaign" },
-      { "field": "spend", "type": "quantitative", "title": "Ad Spend" },
-      { "field": "revenue", "type": "quantitative", "title": "Revenue" }
-    ]
-  }
-}
-```
-
-### Pie chart
-
-```vega-lite
-{
-  "$schema": "https://vega.github.io/schema/vega-lite/v5.json",
-  "title": {
-    "text": "Tickets by Status",
-    "subtitle": "Share of tickets in each workflow state"
-  },
-  "data": {
-    "values": [
-      { "status": "Open", "count": 42 },
-      { "status": "In Progress", "count": 27 },
-      { "status": "Resolved", "count": 58 }
-    ]
-  },
-  "mark": { "type": "arc", "innerRadius": 40 },
-  "encoding": {
-    "theta": { "field": "count", "type": "quantitative", "title": "Tickets" },
-    "color": { "field": "status", "type": "nominal", "title": "Status" },
-    "tooltip": [
-      { "field": "status", "type": "nominal", "title": "Status" },
-      { "field": "count", "type": "quantitative", "title": "Tickets" }
-    ]
-  }
-}
-```
-
-### Histogram
-
-```vega-lite
-{
-  "$schema": "https://vega.github.io/schema/vega-lite/v5.json",
-  "title": {
-    "text": "Order Value Distribution",
-    "subtitle": "Histogram of order totals in the filtered result set"
-  },
-  "data": {
-    "values": [
-      { "order_total": 24 },
-      { "order_total": 31 },
-      { "order_total": 39 },
-      { "order_total": 42 },
-      { "order_total": 63 },
-      { "order_total": 78 },
-      { "order_total": 95 }
-    ]
-  },
-  "mark": "bar",
-  "encoding": {
-    "x": { "bin": true, "field": "order_total", "type": "quantitative", "title": "Order Total" },
-    "y": { "aggregate": "count", "type": "quantitative", "title": "Count" },
-    "tooltip": [
-      { "aggregate": "count", "type": "quantitative", "title": "Count" }
-    ]
-  }
-}
-```

package/custom/skills/fetch_data/SKILL.md

@@ -1,31 +0,0 @@
-name: fetch_data
-description: Fetch one or more records. Use to find records entities. To use this skill you first need to call get_resource tool to know resource column names. This tool returns only atomic record(s) not capable with any aggregations.
----
-
-# Involved tools
-
-You can use tool `get_resource_data` it returns one or more records and is capable of using filters
-
-When you only need specific fields, pass `columns` with the exact resource column names you need. This keeps large result sets small. For record links or user-facing record choices, include the primary key and enough display fields, or omit `columns` when you need the full row context.
-
-# Instructions
-
-To find specific data record you should use filters. ILIKE filters are preferred when we are unsure the input is clear. Pass raw search text to LIKE and ILIKE filters; never wrap filter values in SQL wildcards such as `%`. You can combine filters with OR if you want to search multiple fields. If user queries one record you should try to fetch up to 5 records and if more then one returned return output them all to user and ask to select one. When you communicate about record with user, show its several most important fields.
-
-Every record summary must be based on one exact row returned by `get_resource_data`.
-
-Never combine model/title/name, `_label`, primary key, link, or any field values from different rows.
-
-Never combine fields from different resources in one candidate.
-
-If results come from multiple resources, present them as separate groups with the resource label or resourceId.
-
-If several rows look similar, do not guess which one is "the same" record. Show them separately and ask user to choose.
-
-For long texts show only several first words and add "..." at the end (only if user did not request this field specifically).
-
-Never show information about more than 10 records in one message. If a tool returns more than 10 relevant records, summarize the total count if known, show only the 10 most relevant records, and offer to narrow filters, sort differently, or continue with the next 10.
-
-Also when you communicate with user about record, add related link to this record. Build it as `{ADMIN_BASE_PATH}resource/{resourceId}/show/{primary key}`. Use _label from `get_resource_data` as anchor text for link (use markdown link). Links should always be relative paths and must start with `ADMIN_BASE_PATH`. Do not add an extra slash after `ADMIN_BASE_PATH`.
-
-Before sending the link, verify that the `resourceId`, `{primary key}`, `_label`, and shown fields come from the same exact returned row.

package/custom/skills/mutate_data/SKILL.md

@@ -1,121 +0,0 @@
-name: mutate_data
-description:  Create/update/delete some record of resource or call actions on one or multiple records
----
-
-# Involved tools
-
-Use `create_record` for creating records.
-
-Use `update_record` for editing records.
-
-Use `delete_record` for deleting records.
-
-Use `start_custom_action` and `start_custom_bulk_action` for resource actions.
-
-# General rules
-
-- if there is a dedicated action for some routine (result of `get_resource` tool call, field actions), prefer this to manual updating of records, for example, if you want to approve some comment, prefer calling `approve` action instead of updating `approved` field of comment record (because in action there might be some additional logic like sending notification to user, updating some counters and so on)
-
-## Mutation context
-
-Before performing any state mutation including action calls edit/delete please fetch record which is going to be edited/deleted and show user record in format field → value (show several most important fields which can help user to understand what exactly record he is going to edit or delete).
-
-Every mutation description must describe one exact fetched row. Never combine `_label`, primary key, link, or field values from different rows or different resources in one description.
-
-For field values with long texts show only several first words and add "..." at the end.
-Also please add related link to record with will be changed. Build it as `{ADMIN_BASE_PATH}resource/{resourceId}/show/{primary key}`. Use _label from `get_resource_data` as anchor text for link (use markdown link). Links should always be relative paths and must start with `ADMIN_BASE_PATH`. Do not add an extra slash after `ADMIN_BASE_PATH`.
-
-Before calling the mutation tool, verify that the `resourceId`, `{primary key}`, `_label`, and all shown fields come from the same exact fetched row.
-
-Never show information about more than 10 records in one message. If a mutation plan affects more than 10 records, show only the 10 most important examples plus the total count if known.
-
-When creating new record, show user all data which you gonna create.
-
-Do not ask user for textual confirmation. Dangerous tools are approved by the runtime approval UI.
-
-# Calling actions
-
-To call action on some record you can use `start_custom_action` tool,  or `start_custom_bulk_action` if you need to perform action on several records at once. 
-
-Before calling any of this action you should understand whether this action is allowed. User result of `get_resource` tool call and check `action.allowed` - if this attribute is true or is not exists, assume action is allowed. If this attribute is false, action is not allowed, you should warn user that this action is not allowed for him.
-
-### Example
-
-If you want to block some user you can describe the action by saying:
-
-```I am going to block user:
-* Username: john_doe
-* Email: john_doe@example.com
-* IP Country: USA
-* Currently blocked: No // show this field only if it exists in user record
-
-View [John Doe]({ADMIN_BASE_PATH}resource/users/show/123)
-```
-
-## Updating
-
-You can use tool `update_record` tool it updates fields of record. To update `allowedActions.edit` should be set to true and 
-`updated` column `showIn.edit` should be true at the same time. If one of this condition is not met, explain to user that is not allowed to edit
-
-In addition to instructions above show user the table of edits (old value/new value)
-
-### Examples
-
-For example if you gonna modify user record, please share full user info (not only username but also email, ip country - anything which help adminto check that that is correct user). Message could look like this:
-
-```
-I am going to update user:
-* Username: john_doe
-* Email: john_doe@example.com
-* IP Country: USA
-I am going to change email from john_doe@example.com to new_email@example.com
-
-View [John Doe]({ADMIN_BASE_PATH}resource/users/show/123)
-```
-
-
-## Deleting
-
-To delete some record you can use `delete_record` tool. To delete record `allowedActions.delete` should be set to true.
-
-### Example 
-
-If you gonna delete user record, please share full user info (not only username but also email, ip country - anything which help adminto check that that is correct user). Message could look like this:
-
-```I am going to delete user:
-* Username: john_doe
-* Email: john_doe@example.com
-* Signed up: 2024 Jan 1
-* IP Country: USA
-
-View [John Doe]({ADMIN_BASE_PATH}resource/users/show/123)
-```
-
-## Creating
-
-To create new record you can use tool `create_record`. To create record `allowedActions.create` should be set to true.
-
-When calling `create_record` tool pass only columns which have `showIn.create` set to true and `backendOnly` is not set to true.
-
-For decimal fields please use string values with dot as decimal separator.
-
-After creation of new record also show user a link to this record. If several records record were created, show links to all of them in list.
-
-If more than 10 records were created, show links or details for only 10 of them and summarize the remaining count.
-
-Omit any pictures or file paths, you are not capable of doing it. If they are not required all is good, if they are required, explain to user that you are not able to create record because of this reason.
-
-### Working with dates 
-
-When you create or update date or datetime fields, please use ISO format for this. For example, "2024-01-01" for date and "2024-01-01T12:00:00Z" for datetime. If user provides date in different format, try to parse it and convert to ISO format.
-
-### Example
-
-
-```
-I am going to create user:
-* Username: john_doe
-* Email: john_doe@example.com
-
-View [John Doe]({ADMIN_BASE_PATH}resource/users/show/421) # 421 is id of new created record
-```

package/custom/speech_recognition_frontend/AudioLines.vue

@@ -1,43 +0,0 @@
-<template>
-  <div
-    v-for="(height, index) in lineHeights"
-    :key="index"
-    class="bg-white w-[0.2rem] rounded-sm transition-all duration-100 ease-out"
-    :style="{ height }"
-  />
-  <p v-if="isRecording" class="text-white ml-2">{{ $t('End') }}</p>
-</template>
-
-<script setup lang="ts">
-import { computed } from 'vue';
-
-const IDLE_LINE_HEIGHTS = [0.5, 1, 0.75, 0.5];
-const RECORDING_LINE_WEIGHTS = [0.45, 1, 0.75, 0.9, 0.55];
-const MIN_RECORDING_HEIGHT = 0.25;
-const MAX_RECORDING_DELTA = 0.9;
-
-const props = defineProps<{
-  showAnimation: boolean;
-  isRecording: boolean;
-  amplitude: number;
-}>();
-
-const normalizedAmplitude = computed(() => {
-  if (!props.isRecording || !props.showAnimation) {
-    return 0;
-  }
-
-  return Math.min(Math.max(props.amplitude, 0), 1);
-});
-
-const lineHeights = computed(() => {
-  if (!props.isRecording) {
-    return IDLE_LINE_HEIGHTS.map((height) => `${height}rem`);
-  }
-
-  return RECORDING_LINE_WEIGHTS.map((weight) => {
-    const height = MIN_RECORDING_HEIGHT + normalizedAmplitude.value * MAX_RECORDING_DELTA * weight;
-    return `${height}rem`;
-  });
-});
-</script>

package/custom/speech_recognition_frontend/MicrophoneButon.vue

@@ -1,185 +0,0 @@
-<template>
-  <div
-    v-show="!agentStore.isResponseInProgress || isAudioChatMode"
-    class="absolute bottom-2 flex items-center justify-center z-10 gap-4"
-    :class="[!agentStore.isAudioChatMode ? 'right-16': agentStore.isMobile ? 'right-1/2 translate-x-1/2' : 'right-1/2 translate-x-1/2']"
-  > 
-    <button 
-      v-if="isAudioChatMode && microphoneButtonMode === 'generating'"
-      class="bg-red-500 hover:bg-red-600 dark:bg-red-700 dark:hover:bg-red-800 h-9 flex items-center justify-center rounded-full gap-2 text-white px-4"
-      @click="stopCurrentGeneration()"
-    >
-      <div class="w-3 h-3 bg-white rounded-full"/>
-      {{ $t('Stop') }}
-    </button>
-    <button
-      v-else 
-      class="h-9 bg-lightPrimary dark:bg-darkPrimary 
-        hover:opacity-90 rounded-full flex items-center justify-center
-        transition-all duration-300 ease-in-out overflow-hidden"
-      :class="[isAudioChatMode ? 'w-32 px-2': 'w-9']" 
-      @click="toggleChatMode"
-    >
-      <div class="w-5 h-5 flex items-center justify-center">
-        <div v-if="microphoneButtonMode === 'listen' || microphoneButtonMode === 'off'" class="flex justify-evenly items-center gap-[0.1rem]">
-          <AudioLines
-            :showAnimation="showAudioWavesAnimation"
-            :isRecording="microphoneButtonMode === 'listen'"
-            :amplitude="audioAmplitude"
-          />
-        </div>
-        <div v-else-if="microphoneButtonMode === 'generating'" class="flex items-center justify-center gap-2 text-white text-sm">
-          <span class="w-3 h-3 bg-white rounded-sm" />
-          {{ $t('End') }}
-        </div>
-        <Spinner v-else class="w-4 h-4 text-lightButtonsText dark:text-darkButtonsText fill-lightButtonsBackground dark:fill-darkPrimary" />
-      </div>
-    </button>
-  </div>
-</template>
-
-
-<script setup lang="ts">
-import { computed, onMounted, onBeforeUnmount, ref, watch } from 'vue';
-import debounce from 'lodash.debounce';
-import { requestMicAndStartVAD, stopUserMedia, getRecord } from './voiceActivityDetection';
-import { Spinner } from '@/afcl'
-import { storeToRefs } from 'pinia';
-import { useAgentStore } from '../composables/useAgentStore';
-import { useAgentAudio } from '../composables/useAgentAudio';
-import AudioLines from './AudioLines.vue';
-
-const agentStore = useAgentStore();
-const agentAudio = useAgentAudio();
-const { sendAudioToServerAndHandleResponse } = agentAudio;
-const { stopGenerationAndAudio } = agentAudio;
-const { stopCurrentAudioPlayback } = agentAudio;
-const { agentAudioMode } = storeToRefs(agentAudio);
-const { unlockAudio } = agentAudio;
-const microphoneButtonMode = ref<'off' | 'listen' | 'transcribing' | 'generating'>('off');
-const showAudioWavesAnimation = ref(false);
-const audioAmplitude = ref(0);
-const hideAnimationDebounced = debounce(() => {
-  showAudioWavesAnimation.value = false;
-}, 100);
-const sendUserRecordDebounced = debounce(() => {
-  sendRecordForTranscription();
-}, 500);
-
-const isAudioChatMode = computed(() => agentStore.isAudioChatMode);
-
-onMounted(() => {
-  agentStore.registerOnBeforeChatCloseCallback(async () => {
-    if(agentStore.isAudioChatMode) {
-      onStopRecording();
-      resetAll();
-      agentStore.setIsAudioChatMode(false);
-    }
-  });
-});
-
-watch(agentAudioMode, async (newVal) => {
-  if(newVal === 'streaming') {
-    stopCurrentAudioPlayback(true);
-    microphoneButtonMode.value = 'generating';
-  } else if (newVal === 'transcribing') {
-    microphoneButtonMode.value = 'transcribing';
-  } else if (newVal === 'fetchingAudio') {
-    //Generation is done, waiting for audio to be ready
-  } else if (newVal === 'playingAgentResponse') {
-    // Audio is playing' 
-  } else if (newVal === 'readyToRespond') {
-    if(isAudioChatMode.value) {
-      microphoneButtonMode.value = 'listen';
-      await unlockAudio();
-      await requestMicAndStartVAD(saidSomething, stopRecording, onAnySound);
-      agentAudio.playBeep(1000);
-    } else {
-      microphoneButtonMode.value = 'off';
-    }
-  }
-})
-
-function stopCurrentGeneration() {
-  stopGenerationAndAudio();
-  agentAudio.playBeep(1000);
-}
-
-function toggleChatMode() {
-  agentStore.setIsAudioChatMode(!isAudioChatMode.value);
-  if (isAudioChatMode.value) {
-    onStartRecording();
-  } else {
-    resetAll();
-    onStopRecording();
-  }
-}
-
-async function onStartRecording() {
-  await unlockAudio();
-  await requestMicAndStartVAD(saidSomething, stopRecording, onAnySound);
-  microphoneButtonMode.value = 'listen';
-  agentAudio.playBeep(1000);
-}
-
-function onStopRecording() {
-  agentAudio.playBeep(600);
-  stopUserMedia();
-  audioAmplitude.value = 0;
-  showAudioWavesAnimation.value = false;
-}
-
-function resetAll() {
-  stopGenerationAndAudio();
-  microphoneButtonMode.value = 'off';
-  audioAmplitude.value = 0;
-  showAudioWavesAnimation.value = false;
-  hideAnimationDebounced.cancel();
-  sendUserRecordDebounced.cancel();
-}
-
-
-function saidSomething() {
-  showAudioWavesAnimation.value = true;
-  hideAnimationDebounced();
-  sendUserRecordDebounced();
-}
-
-function stopRecording() {
-  hideAnimationDebounced.cancel();
-  sendUserRecordDebounced.cancel();
-}
-
-function onAnySound(amplitude: number) {
-  audioAmplitude.value = Math.min(Math.max(amplitude, 0), 1);
-
-  if(amplitude < 0.01) {
-    audioAmplitude.value = 0;
-    showAudioWavesAnimation.value = false;
-    return;
-  }
-  showAudioWavesAnimation.value = true;
-  hideAnimationDebounced.cancel();
-}
-
-async function sendRecordForTranscription() {
-  showAudioWavesAnimation.value = false;
-  const recordBlob = await getRecord();
-  if (recordBlob) {
-    onStopRecording();
-    await sendAudioToServerAndHandleResponse(recordBlob);
-  } else { 
-    console.error('No audio recorded');
-  }
-}
-
-onBeforeUnmount(() => {
-  stopUserMedia();
-  agentStore.setIsAudioChatMode(false);
-  onStopRecording();
-  hideAnimationDebounced.cancel();
-  sendUserRecordDebounced.cancel();
-});
-
-
-</script>

package/custom/speech_recognition_frontend/types/voice-activity-detection.d.ts

@@ -1,22 +0,0 @@
-declare module 'voice-activity-detection' {
-  type VADOptions = {
-    fftSize: number,
-    bufferLen: number,
-    smoothingTimeConstant: number,
-    minCaptureFreq: number,         // in Hz
-    maxCaptureFreq: number,        // in Hz
-    noiseCaptureDuration: number, // in ms
-    minNoiseLevel: number,         // from 0 to 1
-    maxNoiseLevel: number,         // from 0 to 1
-    avgNoiseMultiplier: number,     // from 0 to 1
-    onVoiceStart?: () => void;
-    onVoiceStop?: () => void;
-    onUpdate?: (value: number) => void;
-  };
-
-  export default function vad(
-    audioContext: AudioContext,
-    stream: MediaStream,
-    options: VADOptions,
-  ): void;
-}