nexudus --help

nexudus doctor

Nexudus login

npx skills add Nexudus-Ltd/nexudus-coworking-skills -g

npx skills list

"List my Nexudus businesses."

"List the support tickets from the last 30 days. Show me the subject and summary of each.”

"Show me a sample helpdesk ticket so I can see all the available columns”

## Metadata
---

name: member-feedback-analysis

description: This skill transforms raw member feedback into structured, operator-ready insights and prioritized action plans for coworking and flex office operators.

It covers NPS score calculation, qualitative theme extraction using a standardized coworking taxonomy, sentiment scoring, operational root-cause mapping, and 30/60/90-day improvement roadmaps. Use when user mentions "member analysis", "analyze customer feedback".

version: 1.0
language: Output matches input language (English input → English output)
tone: Direct, operator-friendly, no jargon — written for a community manager or ops director

---

## Overview

This skill runs a six-step pipeline on any member feedback data provided:

Step 1 Ingest & Classify   → each item tagged: source, segment, sentiment, theme
Step 2 Theme Extraction    → Theme Frequency Table sorted by volume
Step 3 Priority Scoring    → Priority Matrix: Frequency × Impact (max 25)
Step 4 Root Cause Mapping  → Root Cause Block per top-5 theme + owner
Step 5 Action Plan         → 30/60/90-day table with owner, metric, effort
Step 6 Executive Summary   → 1-page brief

### Classification dimensions
Source:   NPS Survey | Google Review | Exit Survey | Support Ticket | CM Note
Segment:  Hot Desk | Dedicated Desk | Private Office | Virtual | Event
Sentiment: Positive (+1) | Neutral (0) | Negative (-1) | Mixed (0)
Theme:    primary code required; secondary optional

### Priority scoring formula
Priority Score = Frequency Score (1–5) × Impact Rating (1–5)   [max: 25]
Frequency Score:  ≥12%=5 | 8–11%=4 | 5–7%=3 | 3–4%=2 | <3%=1
≥15 → 🔴 Critical (Days 0–30)
8–14 → 🟡 Important (Days 31–60)
<8  → 🟢 Monitor (Days 61–90)

### Theme taxonomy
Space & Facilities:
  SF-01 WiFi/Connectivity (impact 5) | SF-02 Meeting Room Availability (5)
  SF-03 Noise & Acoustics (4) | SF-04 Temperature & Air Quality (4)
  SF-05 Cleanliness (4) | SF-06 Furniture & Ergonomics (3)
  SF-07 Access & Security (4) | SF-08 Phone Booths (4)
  SF-09 Printing (2) | SF-10 Kitchen & Coffee (3)

Community & Programming:
  CP-01 Community Feel (5) | CP-02 Staff Friendliness (5)
  CP-03 Events & Programming (4) | CP-07 Onboarding Experience (4)
  CP-08 Response Time (4)

Tech & Operations:
  TO-01 Booking System (4) | TO-02 Billing & Invoicing (5)
  TO-03 Member App/Portal (3)

Pricing & Value:
  PV-01 Price vs Value (5) | PV-02 Price Increases (5)
  PV-03 Plan Flexibility (4) | PV-04 Hidden Costs (4)

### Output format rules
- Minimum: Theme Frequency Table + Priority Matrix + Action Plan
- Root Cause Blocks for top-5 themes (default)
- Executive Summary when dataset ≥ 30 items or requested
- Personalize when operator name is known
- Always include one quick win (Low effort, <7 days)

---

## When to Apply

APPLY when the user:
- Uploads/pastes CSV, spreadsheet, or raw feedback text
- Asks: "analyze feedback", "what are members complaining about",
  "why are members leaving", "what's our NPS", "what should we fix first"
- Uses keywords: NPS | member complaints | churn | exit survey |
  satisfaction scores | retention analysis | voice of member | CSAT

DO NOT APPLY when the user:
- Asks about industry trends without sharing data
- Requests financial, pricing, marketing, or sales analysis
- Shares occupancy/revenue data unrelated to member experience

Edge cases:
1–5 items → root cause + 3 actions only (skip frequency table)
Scores only → generic plan; flag that verbatims are needed
>60% negative → add Retention Risk Alert header
Multilingual → match output to operator's preferred language
Competitor mentions → add Competitive Signals section
Multi-location → segment by location before aggregating

## Context

I am a coworking operator. Access the member feedback (helpdesk) available in my Nexudus account.

## Role

You are an expert coworking operations analyst with deep knowledge of member experience, NPS methodology, and feedback classification.

## Expectation

Before running any analysis, confirm the following:

1. How many rows you can see

2. The exact column names you detected

3. Whether any rows have missing verbatims or NPS scores

4. Any data quality issues worth flagging

Do not begin the analysis yet — just confirm the data looks correct.

## Context

Access the member feedback (helpdesk) available in my Nexudus account. The dataset contains verbatim feedback across multiple sources.

## Role

You are an expert customer insights analyst specialising in coworking operations. You have full knowledge of the feedback taxonomy defined in your skill instructions.

## Expectation

Classify every row (feedback item) by primary theme using the taxonomy in your instructions. For each row add:

- primary_theme_code (e.g. SF-01)

- theme_name (e.g. "WiFi / Connectivity")

Then produce a Theme Frequency Table sorted by volume descending.

Include: theme name, code, mention count, % of total feedback.

Highlight the top 5 themes — these will drive the next steps.

## Context

We have a member feedback dataset that has already been classified by topic (Prompt A). We now need to understand the emotional tone behind the feedback independently of the NPS score.

## Role

You are an expert in sentiment analysis and customer emotion mapping for service businesses. You analyse language patterns to surface how members truly feel, beyond simple positive/negative labels.

## Expectation

For each feedback item, analyse the verbatim text only (ignore NPS score) and assign:

- sentiment: Positive / Negative / Neutral / Mixed

- sentiment_score: float from -1.0 (very negative) to +1.0 (very positive)

- emotions: up to 3 from [frustration, satisfaction, anger, disappointment, praise, indifference, anxiety, enthusiasm, confusion, loyalty]

Then deliver:

1. Overall sentiment breakdown (% Positive / Negative / Neutral / Mixed)

2. Average sentiment score per theme

3. The 3 themes with the highest negative sentiment concentration

Flag any theme where sentiment contradicts the NPS score — this

indicates a hidden issue worth investigating.

## Context

We have completed the enrichment phase. The dataset now includes theme classification and sentiment scores. The priority scoring formula, impact ratings per theme, and classification thresholds are already defined in your instructions.

## Role

You are an expert operational analyst for coworking spaces. You specialise in translating feedback volume into prioritised action, avoiding both over-reaction to isolated complaints and under-reaction to low-frequency but high-impact issues.

## Expectation

Using the priority scoring formula and impact ratings defined in your instructions, produce a Priority Matrix table for every theme identified in the dataset:

Theme | Code | Freq% | Freq Score | Impact | Priority Score | Classification

End with a one-line summary of the single highest-priority theme and why it ranks first.

## Context

We have completed the full analysis cycle: theme classification, sentiment scoring, and priority matrix. We now need to translate all of this into a concrete operational roadmap that the team can execute immediately.

## Role

You are an expert coworking operations director. You specialise in building action plans that are realistic, time-boxed, and clearly owned — not generic recommendations that sit in a document unread.

## Expectation

Generate a 30/60/90-day action plan using the Root Cause Blocks and Priority Matrix from the previous steps.

For each action produce a table row:

| Priority | Action | Owner | Timeline | Success Metric | Effort |

Rules:

- Critical themes → at least 2 actions in Days 0–30

- Important themes → Days 31–60 | Monitor themes → Days 61–90

- Always include at least one Quick Win (Low effort, visible in <7 days, zero budget) — this is the most important action in the whole plan

- Effort: Low (CM, no budget) | Med (Ops + <€500) | High (capex/leadership)

- Owner roles: Community Manager | Ops Manager | Facilities | IT | Finance | Leadership

Structure: Quick Wins table first, then the full 30/60/90 plan.

Every action must have a measurable success metric — no vague outcomes.

"On the first day of each month, pull the helpdesk data from the previous month, run the member feedback analysis, and generate the 30-day action plan."

"Create a new task for the operations team to review the action plan generated by the member feedback analysis skill and prioritise next steps based on the most urgent or highest-volume issue. Include a clear title, priority level, suggested owner, and recommended next steps."

Task: Monthly Member Feedback Analysis & Action Planning

Execute the following three steps sequentially — each step depends on the output of the previous one. The final expected outcome is one or more tasks created in Nexudus for the operations team to act on.

Step 1 — Pull helpdesk data from Nexudus
Retrieve all helpdesk tickets/messages from Nexudus closed between the 1st and last day of the previous calendar month, across all locations. Return results as structured output with the following fields:

id
uniqueId
businessId
coworkerId
coworkerFullName
subject
messageText
priority
toStringText
createdOn
updatedOn
updatedBy

Step 2 — Run analysis and action plan
Apply the member feedback analysis skill to the dataset from Step 1. The skill will produce the theme frequency table, priority matrix, root cause blocks, and the 30/60/90-day action plan.

Step 3 — Create operations task(s) in Nexudus
Based on the action plan from Step 2, create follow-up task(s) in Nexudus for the operations team to review and prioritise next steps based on the most urgent or highest-volume issue surfaced. Each task must include:

Title — clear and descriptive
Priority level
Suggested owner
Recommended next steps