ever-just
- 131 skills
- 0 followers
- 6 hours ago last updated
- ▌ Tdd · ever-just bundleTest-driven development — the red/green/refactor loop, what makes a test worth keeping (behavior through public interfaces, not implementation details), where tests go (seams agreed up front), and the anti-patterns that make tests lie (implementation-coupled, tautological, horizontal-sliced). Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests written well.
- ▌
- ▌
- ▌
- ▌ Handoff · ever-justCompact the current conversation into a standalone handoff document so a fresh agent session can pick up the work with full context — what's done, what's outstanding, decisions made and why, and which skills the next session should invoke. Use when a session is ending, running low on context, or the user explicitly wants to continue this work in a new session (including a different machine or agent).
- ▌
- ▌ Grilling · ever-justRun a relentless, one-question-at-a-time Socratic interview to stress-test a plan, decision, or idea before acting on it — walk each branch of the decision tree, propose a recommended answer for every question, look up anything discoverable from the environment instead of asking, and don't act until the human confirms shared understanding. Use when the user wants their thinking stress-tested, asks to be "grilled" about something, or when a plan has enough open decisions that charging ahead risks building the wrong thing.
- ▌
- ▌ Wayfinder · ever-justPlan a piece of work too big for one agent session as a shared map of decision tickets on an issue tracker (or local markdown files), then resolve the tickets one at a time — across as many sessions as it takes — until the way to the destination is clear. Use when a loose idea is too big to execute in one sitting, when a long-horizon initiative keeps stalling because nothing tracks its open decisions between sessions, or when several stale/parked efforts need one place that shows what's actually left to decide.
- ▌
- ▌ Godaddy API · ever-justManage GoDaddy domains and DNS records via the official GoDaddy Developer Portal REST API (developer.godaddy.com). Use when user needs to list domains, update DNS records, check domain availability, or automate domain management tasks.
- ▌
- ▌ Everjust Sms · ever-justOperate the SMS app of an everjust.app tenant (send an SMS to a number, send SMS as chatter on a partner/lead, use an SMS template, mass-SMS a set of records, inspect delivery state, and reason about which gateway a send actually took) via the Odoo MCP/ORM. Use when the task is to text someone from an everjust.app workspace, diagnose why an SMS failed, check an sms.sms row's status, or confirm which provider (TextBee / Ringover / Twilio / Odoo IAP) the tenant is on. This is the everjust_sms_gateway stack — the transport under sms.sms is provider-SWAPPED per company via res.company.sms_provider, NOT necessarily Odoo IAP. Do NOT hand-POST TextBee/Ringover; drive sms.sms/sms.composer and let _get_sms_api_class route it. Cross-references [[everjust-platform]] and [[everjust-agent-mcp]]; sibling of [[everjust-mail-ops]].
- ▌ Everjust Sign · ever-justOperate the "Sign" e-signature app of an everjust.app tenant (create a signable PDF request, add typed signers by role, send it out for signature, track who has signed, download the finished signed PDF, and read the tamper-evidence log) via the Odoo MCP/ORM. Use when the task is to send a document out for signature from an everjust.app workspace, check a signature request's status, find pending signers, generate a request from a reusable template, or verify a signed document's integrity hash. This is the OCA sign_oca stack (sign.oca.request / .signer / .template) — NOT Odoo Enterprise "Sign" (sign.request/sign.item) and NOT DocuSign. Signers sign in a public portal via a tokenized link; invite emails go out through Odoo chatter (message_notify), so they ride the everjust mail send-gates — see [[everjust-mail-ops]]. Cross-references [[everjust-platform]] and [[everjust-agent-mcp]]; sibling of [[everjust-sms]] and [[everjust-mail-ops]].
- ▌
- ▌ Github Search · ever-justSearch GitHub effectively — repositories, code, and topics — using the official GitHub docs' search syntax. Use when hunting for a repo/framework/library that does X, locating code patterns across public GitHub, or building a discovery query matrix for research. Covers repository search qualifiers, the code-search syntax (boolean/regex/path/symbol), the REST search API with rate limits, and a repeatable find-a-framework playbook. Grounded in docs.github.com (fetched 2026-07); re-fetch the linked docs pages if a qualifier seems to misbehave.
- ▌
- ▌ UX Evaluation · ever-just bundleEvaluate user experience by locating decisions on a layered framework drawn from Jesse James Garrett's Elements of User Experience and modern frontend practice. Use this skill when reviewing or auditing any product interface, when diagnosing a UX problem (where does it actually live?), when designing or systematizing a frontend, when discussing information architecture, interaction design, layout, design tokens, or design systems, when asked questions like "is this a UI problem or a deeper problem", "what should we systematize", "where should this decision be made", or any request to evaluate, critique, or improve a digital product holistically. Trigger this skill whenever a question touches the structure of a product rather than just its surface — even if the user doesn't say "UX" explicitly.
- ▌ Web Visibility · ever-justMake a site or product maximally findable by search engines AND AI answer engines (ChatGPT Search, Perplexity, Google AI Overviews). Use when building visibility into a product, auditing a site's SEO/AEO/GEO, or deciding which discoverability mechanism is worth implementing. Evidence-based: prioritizes structured data and proven content patterns, and explicitly skips the hype (llms.txt-as-SEO, FAQ rich results, Indexing API). Includes JSON-LD recipes, robots.txt/llms.txt/IndexNow generators, and a validation step.
- ▌ Diagnosing Bugs · ever-justDiagnosis loop for hard bugs and performance regressions — build a tight red/green feedback loop before hypothesizing, then reproduce, minimize, rank hypotheses, instrument, fix with a regression test, and clean up. Use when the user says "diagnose"/"debug this", or reports something broken, throwing, failing, or slow, especially when the cause isn't obvious from reading the code.
- ▌ Everjust Events · ever-justOperate the Events app of a live everjust.app tenant (create/publish an event, take & manage attendee registrations, wire registrations to CRM leads, schedule attendee email/SMS reminders, inspect seats/registration state) via the Odoo MCP/ORM. Use when the task is to set up or edit an event on an everjust.app workspace, register/confirm/cancel an attendee, turn registrations into crm.leads, add or diagnose a registration confirmation/reminder email or SMS, check seat availability, or reason about which event modules are installed on a tenant. This is STOCK Odoo event/website_event/event_crm/event_sms — NO custom everjust event addon — but website_event_track (event.track / speakers / agenda) is installed on ONLY some tenants, and event_sms reminders ride the per-company everjust SMS gateway swap. Cross-references [[everjust-platform]], [[everjust-agent-mcp]]; SMS via [[everjust-sms]], leads via native CRM, event mail is stock event.mail (NOT the [[everjust-mail-ops]] webmail stack).
- ▌ Github Research · ever-justSearch GitHub intelligently to find specs, reference implementations, library adopters, and config patterns. Use when research means locating code, repos, or examples on GitHub — pick the right surface (REST/web search vs GraphQL vs code search), the right qualifiers, and the right tool (gh CLI or mcp__github__*), then rank and verify results. Covers rate limits, the 1,000-result cap, and a goal->tool decision guide.
- ▌
- ▌ Everjust Website · ever-justManage the public marketing site of an everjust.app (Odoo 19) tenant through the everjust_agent_mcp WEBSITE tools — list/create/edit pages (copy-on-write QWeb arch), nav menus, 301/302 redirects, per-page SEO metadata, publish/schedule/index state, and page visibility. Use when the task is to edit a marketing page's content, add or reorder a nav menu item, create a redirect, set a page's title/description/OG image for SEO, publish/unpublish/schedule a page, or understand the /-vs-/odoo debrand and the public-website gate. The everjust marketing pages (website_connectdomain, website_tcsw) are VERBATIM Tailwind-utility QWeb wrapped in <t t-call="website.layout">, NOT drag-drop snippets — you edit the QWeb arch and reuse the existing Tailwind classes. Requires an admin / website-designer Odoo role. NOT for backend business data and NOT for DNS/SSL of a customer's OWN domain (the Connect Domain product). Cross-references [[everjust-platform]] and [[everjust-agent-mcp]].
- ▌
- ▌ Everjust Mail Ops · ever-justOperate the everjust.app NATIVE mail platform (send/receive as a mailbox, inspect a domain's verification, read a mailbox's entries, check suppression) via the Odoo MCP/ORM. Use when the task is to send an email as an everjust.app tenant address, read/triage a mailbox, diagnose why a send is blocked, check a sending domain's DKIM/verification state, or verify a bounce/complaint suppression. This is the everjust.mail.* stack (custom webmail), NOT Odoo Discuss and NOT raw mail.mail — do not reach for mail.thread/Discuss/message_post, and do not hand-roll mail.mail even via a raw Odoo API key that bypasses the MCP (it can deliver while staying invisible in the mailbox UI). Send through compose_send or the MCP's mail_send tool only. Always read the returned delivery result; a filed Sent entry is not proof of delivery. Cross-references [[everjust-platform]] and [[everjust-agent-mcp]].
- ▌
- ▌ Everjust Projects · ever-justOperate the "Projects" app of an everjust.app Odoo 19 tenant (project.project / project.task) over the everjust_agent_mcp MCP — create/find projects and tasks, move a task across kanban stages, assign it, set deadlines, add tags, manage personal to-dos, and send/trigger a stage SMS. Use when the task is to read or mutate a tenant's projects, tasks, task stages, or tags; to move work through a kanban pipeline; to file or triage a personal to-do; or to understand why a stage-move SMS did or didn't go out. This is STOCK Odoo project + project_todo + project_sms — the everjust twist is only the SMS transport (swapped to TextBee/Ringover via everjust_sms_gateway) and Odoo-19 field renames (task.state, not kanban_state). Cross-references [[everjust-platform]], [[everjust-agent-mcp]], and [[everjust-mail-ops]].
- ▌
- ▌
- ▌ Everjust Agent MCP · ever-justConnect to and operate an EverJust.app (Odoo) tenant through its built-in Model Context Protocol server at https://<tenant>.everjust.app/mcp. Use when you need to read, create, update, or delete records in a customer's EverJust/Odoo workspace (CRM leads, contacts, invoices, projects, events, tasks, products, anything in Odoo) from Claude Code or Codex — authenticating as an Odoo user via their API key so every operation is role-bounded and audited. Also use when the user says "connect to my everjust workspace", "add the everjust MCP", "query my Odoo over MCP", or asks how to configure the everjust MCP server.
- ▌
- ▌ Everjust Documents · ever-justOperate the "Documents" app of an everjust.app Odoo 19 tenant (browse/create/move folders and files, upload, download, tag, migrate storage, point Documents at the tenant's private cloud) via the Odoo MCP/ORM. Use to read or mutate a tenant's documents — create a folder (dms.directory) or file (dms.file), fetch a file's bytes, move/archive/lock/tag a file, or wire the app to Nextcloud-over-WebDAV. This is the OCA dms stack (dms.file / dms.directory / dms.storage) plus the bespoke everjust_documents layer that stores every file PHYSICALLY in the tenant's Nextcloud over WebDAV (fs_storage + fs_attachment) — NOT Odoo Enterprise "documents.document" (that model does not exist here), NOT raw ir.attachment. Only some tenants have it installed (tcstartupweek + headsup as of 2026-07, NOT connectdomain) — check first. Files depend on live Nextcloud connectivity and a webdav4 monkeypatch. Cross-refs [[everjust-platform]], [[everjust-agent-mcp]], [[everjust-mail-ops]], [[everjust-sms]].
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌ LLM Deeplink Widget · ever-justBuild an "Ask AI about us" widget — a row of icon buttons that deep-link a visitor into their own LLM app (ChatGPT, Claude, Perplexity, Google AI Mode, Grok) with a prompt pre-filled about the product or page. Use this skill whenever the user wants "ask AI" / "open in ChatGPT" / "explain this with AI" buttons, LLM deep links, a way for visitors to learn about the product from their own AI assistant, or wants to add AI-assistant call-to-actions to a site footer, docs, or landing page. Includes the verified per-provider URL schemes and the critical rule that the injected prompt must be self-contained.
- ▌
- ▌ UX Decision Rubrics · ever-justMake UI/UX calls objectively with two rubrics instead of by taste. Rubric A picks the right form control via decisive rules like NN/g's toggle-vs-checkbox test; Rubric B scores each key user flow 1–5 across 7 clarity dimensions to flag which to redesign. Use when choosing a form control, judging whether a flow needs redesign, justifying "objectively better" to a stakeholder, or writing UI acceptance criteria. Not for pure brand/visual work — use `frontend-design`.
- ▌
- ▌ Deploy Log Forensics · ever-justReconstruct what changed on production — which commit, which module, which tenant, at what time — from CI/CD run logs when you have NO server access (no SSH, no cloud credentials). Use when asked "what broke production / when did X appear / which deploy carried this change" and the only evidence available is git history plus the deploy pipeline's own logs. Covers mapping workflow runs to commit ranges, mining job logs for change markers (changed-module lists, per-tenant update sections, restart timestamps), separating the commit that CAUSED a behavior from the commit that EXPOSED it, and the hygiene rules for dispatching diagnostic workflow runs (environment protection rules, temp-commit cleanup). Complements web-deploy-verification (which verifies a change IS live); this skill attributes what went live and when, after the fact.
- ▌ Everjust Website SEO · ever-justSEO + discoverability for an everjust.app (Odoo 19) tenant's public marketing site, via the everjust_agent_mcp MCP as an admin / website-designer user. Use when the task is to set or backfill a page's meta title/description/keywords/OG image/canonical slug (website_meta_* + seo_name on website.page — related proxies onto its ir.ui.view), control sitemap membership or crawlability (website_indexed / website_published / date_publish), add the site's social_* profiles + social_default_image (the seven _SOCIAL_FIELDS feed the everjust_visibility schema.org JSON-LD sameAs on every page so AI engines cite it), edit robots_txt, verify Google Search Console, or enable IndexNow (the everjust_visibility.indexnow_key ir.config_parameter, confirm-gated, plus its opt-in cron). NOT for page CONTENT/layout ([[everjust-website]] / [[everjust-website-snippets]]) nor a customer's OWN-domain DNS/SSL (the Connect Domain product). Cross-references [[everjust-platform]], [[everjust-agent-mcp]], [[everjust-website]].
- ▌
- ▌
- ▌
- ▌ Unmerged Work Census · ever-justFind ALL work that never reached the default branch or production — hidden code on "docs-only" PRs, never-PR'd remote branches, stale local clones in long-lived agent containers, stashes, dangling commits, and history-rewrite ghosts. Use when asked "what haven't we shipped", "find everything not pushed/merged", "did any work get lost", or before deleting old branches. Covers verifying PR descriptions against actual branch diffs (they go stale), git branch --no-merged + git cherry to separate genuinely unique patches from rewritten-history duplicates, ahead/behind local-master drift, spot-verifying that "re-landed" content really exists on the target branch, and the multi-agent reality that every remote session container holds its own clone whose unpushed work is invisible to every other session.
- ▌
- ▌
- ▌ Agent Quality Grading · ever-justGrade AI-agent performance qualitatively — every user↔agent conversation on four axes (did it do the task / respond fast / use the right tools / message quality), plus the generated assets (PDFs, images, videos) and the prompts/configs — using writing-quality skills as the message-quality rubric. Produces per-channel grades, per-agent report cards, asset grades, and prompt grades, each with verbatim evidence.
- ▌
- ▌ Everjust Appointments · ever-justOperate the everjust.app custom Appointments app (online booking → calendar event + optional CRM lead + confirmation email) via the Odoo MCP/ORM. Use when the task is to configure a bookable appointment type and its weekly slots, create/confirm/reschedule/cancel a booking as a tenant, inspect a customer's bookings, diagnose why a public /appointment slot isn't offered (min-advance / max-days / staff conflict), or wire a booking to CRM. This is the BESPOKE everjust_appointment stack (appointment.type / appointment.slot / appointment.booking) — NOT Odoo's stock Enterprise appointment.* models, and NOT calendar.event directly. Only some tenants have it installed. Cross-references [[everjust-platform]] and [[everjust-agent-mcp]]; CRM leads flow to native crm.lead; confirmation email goes through a stock mail.template (NOT [[everjust-mail-ops]]).
- ▌
- ▌
- ▌
- ▌ Parallel Agent Fanout · ever-just bundleBattle-tested methodology for orchestrating many concurrent subagents to build or audit a large dataset — a 3-wave discovery→pull→synthesis pipeline with shared instruction templates, a strict no-delegation rule, file-on-disk completion checks, batching, incremental commits, and a recombine + row-integrity validation step. Use when a task is too large for one context (hundreds of companies/files/records), when you're fanning out research or extraction across batches, when subagents must write results to disk without clobbering each other, or when you need to detect and re-run subagents that stalled or self-delegated. Model-agnostic; complements task/agent tooling.
- ▌
- ▌
- ▌
- ▌
- ▌ Everjust Website Forms · ever-justWire a public website form on an everjust.app (Odoo 19) tenant to a backend model — enable a model as a form target, place the form on a marketing page, and route submissions (Contact-Us → CRM lead, with medium=Website attribution + team/salesperson assignment). Use when the task is to add or fix a Contact-Us / lead-capture / newsletter / task-request form, make a NEW model accept form submissions, understand the POST /website/form/<model> contract and its field whitelist, or set where website leads land (default team / salesperson). Plumbing is stock Odoo website + website_crm (Odoo 19 has NO separate website_form module — the /website/form controller lives in the website addon); drive it via the everjust_agent_mcp WEBSITE tools (the <form> is QWeb in a page arch) plus generic ORM (ir.model.website_form_access, formbuilder_whitelist on ir.model.fields, website.crm_default_team_id). Cross-references [[everjust-website]], [[everjust-crm-sales]], [[everjust-agent-mcp]], [[everjust-platform]].
- ▌ Everjust Website Forum · ever-justOperate the Q&A Forum (website_forum) app of a live everjust.app tenant via the Odoo MCP/ORM — the full ask→answer→accept→close/validate lifecycle plus votes, tags, the karma economy, and moderation. Use when the task is to create/configure a forum.forum, post a question or an answer (answers are forum.post rows with a parent_id, NOT comments), accept the correct answer (is_correct), up/downvote a post, add/retag tags, moderate (validate a pending post, close/reopen, flag, mark offensive), grant a user forum karma, or read forum state. This is STOCK Odoo website_forum + gamification (karma is res.users.karma, a STORED field driven by gamification.karma.tracking) — NO custom everjust forum addon; every write is karma-gated by the forum's karma_* fields and you act as one Odoo user. The public /forum pages are QWeb edited via the website_* tools, NOT this ORM. Cross-references [[everjust-platform]], [[everjust-agent-mcp]], and siblings [[everjust-events]], [[everjust-mail-ops]].
- ▌
- ▌
- ▌ Production Agent Audit · ever-justEnd-to-end methodology for auditing a production AI-agent platform from its REAL logs — census, total multi-source extraction, fan-out analysis, adversarial verification, and graded synthesis. Use when asked to review how deployed AI agents are performing across channels (SMS/email/voice/chat), judge tool-calling/adherence, or produce an objective good-vs-bad report from server logs + database + error tracker.
- ▌
- ▌
- ▌ Everjust Odoo Shell Ops · ever-justOperate an everjust.app (Odoo 19) tenant from the BOX SHELL (SSH + docker), the deploy-pipeline and box-ops layer. Use when the task needs bulk DB writes, DB-only page publishing, clearing the sitemap ir.attachment cache, creating an ir.cron, recovering a CI deploy whose rsync silently did not land, avoiding deploy-collisions across concurrent agents (gh run idle check, scoped git add), restarting Odoo to compile a QWeb edit, or fixing an nginx stale-inode after a config redeploy. Covers the odoo shell invocation, the COW-fork-overrides-generic gotcha, and the Deploy to Production pipeline. The deploy/ops layer around [[everjust-website-customization]] (which owns durable view/CSS/behavior customization from the shell). Prefer the MCP ([[everjust-agent-mcp]], [[everjust-website]]) for ordinary edits; drop to the shell when it cannot. Cross-references [[everjust-platform]], [[github-actions-ec2-deploy]].
- ▌
- ▌
- ▌ Parallel Agent Refactor · ever-just bundleOrchestrate many parallel subagents to run a large multi-file refactor, migration, or codemod sweep SAFELY and fast — partition by disjoint file ownership, fan out one write-agent per independent slice behind typecheck+build barriers, and synthesize their structured returns. Use when adopting a component library across routes, migrating design tokens / dark mode, running a rename or codemod sweep, modernizing per-route, or applying one rubric across a whole codebase — any breadth change that decomposes into independent file sets. Not for interdependent foundation work (shared config, a token layer, coupled modules) — do that inline.
- ▌ Web Deploy Verification · ever-justConfirm a web/site change is ACTUALLY live in production after a merge, instead of reporting success because the merge or CI succeeded. Use after merging a PR that deploys on push (Vercel/Netlify/GitHub Actions/etc.) to a live URL, before telling a user a change has "shipped." Covers polling a live URL for content markers with a bounded background loop, a local-build Playwright screenshot fallback for visual changes (with the headless-Chromium-through-a-proxy and port-race pitfalls that break naive attempts), and why "the build succeeded" and "the deploy is live" are different claims. Complementary to product-specific deployment-testing skills (health checks, CI/CD mechanics for one stack) — this is the generic verification habit, usable on any deploy pipeline.
- ▌
- ▌
- ▌
- ▌ Dark Mode Token Migration · ever-just bundleAdd dark mode to a light-only app that styles with RAW color utilities (Tailwind `stone-*`/`slate-*`/`gray-*`) via a semantic token layer, migrating utilities onto it so light stays PIXEL-IDENTICAL and dark comes for free. Use when asked to "add dark mode", or to refactor hardcoded color utilities into a themeable token system. Not for apps already on semantic tokens — just add `.dark` values plus a toggle.
- ▌ Everjust Website Snippets · ever-justAuthor and edit website content on an everjust.app (Odoo 19, html_builder era) tenant — the s_* snippet triad (QWeb template + t-snippet registration in website.snippets + OWL option Plugin), oe_structure drop-zones vs editable zones, and the "wrap-don't-rewrite" method for making Tailwind-QWeb marketing ports (website_connectdomain / website_tcsw) both agent- and human-editable via s_cd_* blocks. Use when the task is to add/edit a page, drop or build a reusable content block, expose builder options for a block, or safely modify a ported marketing site — via the MCP website_* tools (website_pages / website_new_page / website_edit_page / website_publish / website_menu / website_redirect), which copy-on-write into a site-specific ir.ui.view so module upgrades never clobber the edit. This is html_builder (Odoo 19), NOT the old web_editor/snippet-options.js — options are OWL Plugin classes, not data-attributes. Cross-references [[everjust-platform]] and [[everjust-agent-mcp]].
- ▌
- ▌ Icp Prospect List Builder · ever-just bundleEnd-to-end methodology for building a large, source-cited B2B prospect dataset from public data — define an ICP in searchable terms, discover matching companies across ranked sources (source-code/technographic search, competitor customer bases, software + AI-tool directories, the Product Hunt API, accelerator portfolios), then categorize, ICP-score, dedupe, and pull size-routed decision-maker contacts. Use when asked to find "companies like our customers", build a GTM/sales target list, enumerate a market segment, score prospects for fit, or turn a raw company list into a prioritized, contactable pipeline. Public sources only.
- ▌
- ▌
- ▌ Resolving Merge Conflicts · ever-justResolve an in-progress git merge or rebase conflict by understanding the intent behind each side (commit messages, PRs, issues) before touching a hunk, preserving both intents where possible, then running the project's checks and finishing the operation. Use when you hit a git merge/rebase conflict, or the user asks to resolve one.
- ▌
- ▌ Claude Session Archaeology · ever-justReconstruct what work was actually done on a project by mining Claude Code session transcripts (~/.claude/projects/**/*.jsonl) — streaming grep/jq recipes for files up to 150MB, the CLAUDE.md boilerplate false-positive trap, core/partial/incidental classification, and fork detection. Use when asked "what have we done on X?", when rebuilding a project history, when recovering decisions or work that never reached git, or as the history phase of a footprint inventory.
- ▌ Empirical Responsive Audit · ever-just bundleAudit a web UI for mobile/layout defects EMPIRICALLY by rendering every servable surface across a phone/tablet/desktop viewport matrix (both orientations, light + dark) with a Playwright DOM probe that MECHANICALLY flags horizontal overflow, sub-44px tap targets and sub-16px inputs, then ships the probe as a non-zero-exit pre-merge gate. Use when the frontend "isn't optimized for mobile", text "spills outside its container", small-screen stacking is "awkward", or for any responsive / tap-target / layout audit or checked-in gate. Not for pure visual-taste questions — use `ui-ux-audit` / `frontend-design`.
- ▌ Everjust Calendar Contacts · ever-justOperate the Calendar + Contacts app of an everjust.app tenant over the Odoo MCP/ORM — the shared res.partner contact spine and calendar.event scheduling, with optional Google/Microsoft calendar sync. Use when the task is to create/find/update a contact (person or company), tag/segment contacts with res.partner.category, look up who a partner is before mailing or invoicing them, schedule/reschedule/cancel a calendar.event, add or read attendees and their RSVP state, check a user's free/busy for double-booking, or reason about how a booking became a calendar event. This is STOCK Odoo calendar + contacts with a thin everjust layer (res.partner.is_agent flag, phone/SMS action methods, and everjust_appointment writing events) — NOT a custom webmail or a bespoke scheduler. res.partner is the ONE contact record shared across CRM, mail, projects, invoicing and appointments; edits here ripple everywhere. Cross-references [[everjust-platform]], [[everjust-agent-mcp]], and [[everjust-mail-ops]].
- ▌
- ▌ MCP Server Discoverability · ever-justMake a hosted MCP server (and the REST API behind it) discoverable and usable by AI agents, so agents find and call your tools rather than only humans finding your site. Use this skill whenever the user has an MCP server or a public API and wants AI agents / ChatGPT / Claude to discover and use it, wants to "list our MCP server", "submit to the MCP registry", get into Claude/ChatGPT connector directories, fix "the MCP connection silently fails or won't authenticate", or improve agent-facing (not human) discoverability. Covers the official MCP Registry, the /.well-known OAuth discovery chain that is the
- ▌
- ▌ Programmatic Osint Sources · ever-just bundleCatalog of data-rich OSINT/enrichment sources that can be pulled PROGRAMMATICALLY with low lift — a public URL endpoint, a keyless REST API, or a genuine free-tier API. Use when you have an identifier (email, name, domain, username, phone, company, or IP) and want to turn it into rich machine-readable data: find or verify emails, reverse-lookup a person from an email, enumerate subdomains and infrastructure, check breach/credential exposure, resolve a company to officers/beneficial owners, confirm an account exists on a platform, enrich a phone number, or pivot an identity across ecosystems. Generalizes the "Gravatar returns a profile from an email" trick to hundreds of sources. Covers keyless endpoints, free-key APIs, and cheap paid upgrades, each with a concrete example call and honest auth/ToS/freshness caveats.
- ▌ Reverse Proxy Cms Indexing · ever-justFix SEO and indexing for a CMS (Odoo, or any web app) served behind a Host-rewriting reverse proxy (nginx or Cloudflare), where the app sees a different internal host than the public domain and therefore emits the wrong robots.txt, sitemap, or canonical URLs. Use this skill whenever a site is not getting indexed, robots.txt says Disallow when it should not, the sitemap or canonical tags point at an internal host, an internal tenant host is itself a crawlable duplicate, or page/template edits do not render live, ESPECIALLY on the everjust.app / customdomain.ai Odoo platform. Covers the domain-mismatch robots+noindex bug, nginx sub_filter canonicalization, duplicate-host noindex, the compiled-template render cache, and a safe backup-validate-rollback config-edit process.
- ▌ System Design Architecture · ever-just bundleExhaustive, reference-backed toolkit for designing production-grade software systems end to end — networking through the full backend stack. Use when architecting or reviewing a backend/SaaS, scaling a service from low volume toward millions of users, hardening for security, determining capacity limits/thresholds, projecting cloud cost, choosing an architecture archetype (monolith, microservices, event-driven, serverless, multi-tenant SaaS, multi-agent/LLM), enumerating the product layers a system needs, picking API/network open standards (OpenAPI, gRPC, OAuth, OpenTelemetry), or selecting cloud provider services (AWS/GCP/Azure/Cloudflare). Bundles decision frameworks, review checklists, a worked example, and a deep link-rich reference library. Load the reference file that matches the sub-problem; do not answer high-stakes design questions from memory when a bundled reference covers it.
- ▌
- ▌
- ▌ Product Footprint Inventory · ever-justItemize everything a product or company encompasses — code, running infrastructure, web/social presence, data, written IP, commercial rails, ecosystem position, and the development history — by fanning out read-only agents across ~12 dimensions and mining the agent-session transcripts. Use when preparing to sell or buy a product, planning a carve-out, building a data room, answering "what do we actually own", or onboarding to a sprawling estate nobody has mapped.
- ▌ Temporal Finding Validation · ever-justCross-check each audit finding's REAL observation timestamp against the commit/deploy timeline (with timezone normalization) to decide whether it is STILL LIVE or already fixed by a commit — so you never report a resolved issue as open (or a still-broken one as fixed). Use to validate a findings list against git history before finalizing an audit.
- ▌