| 1. |
This skill provides help documentation for Centralpoint data management features.
|
| 2. |
The Data Transfer module moves data from any source to any destination. Common scenarios:
|
| 3. |
|
| 4. |
Converts plain English descriptions of AI tasks into fully-formed Centralpoint Prompt Manager records. Includes Live Mode which queries the CP Web API to discover real module field names and values before writing When/If/Do conditions.
|
| 5. |
This skill provides help documentation for Centralpoint modules features.
|
| 6. |
Help Centralpoint users create HTML, JavaScript, and CSS. When dynamic content is needed, include the appropriate CpScript tags using `` syntax.
|
| 7. |
This skill teaches how to build **JavaScript-powered action buttons** inside Centralpoint DataSource Item Content that fire POST requests to Web API (`api.svc`) endpoints. The buttons use server-rendered `[cp:scripting]` values to build JSON payloads
|
| 8. |
JSON Structure and Syntax J
|
| 9. |
|
| 10. |
This skill provides help documentation for Centralpoint admin utilities features.
|
| 11. |
Enforces that all AI-generated SQL is SELECT-only and free from injection vectors. This is the highest-priority security guardrail in the platform. Applies to every AI task involving SQL generation regardless of context, module, or user role.
|
| 12. |
PoliciesExport
|
| 13. |
|
| 14. |
|
| 15. |
|
| 16. |
|
| 17. |
|
| 18. |
|
| 19. |
|
| 20. |
|
| 21. |
|
| 22. |
|
| 23. |
|
| 24. |
**COPYRIGHT (C) 2025 Oxcyon, Inc. -- Centralpoint Digital Experience Platform**
|
| 25. |
**Architecture rule:** A Centralpoint Module Designer always binds to its own
|
| 26. |
|
| 27. |
|
| 28. |
|
| 29. |
Title of Document 5 Date: 12/1/2020 SSEID: 112233 Name: Bob Smith Body copy dealing with Japan Body copy dealing with Japan Body copy dealing with Japan Body copy dealing with Japan Body copy dealing with Japan Body copy dealing with Japan Body copy dealing with Japan Body copy dealing with Japan Body copy dealing with Japan Body copy dealing with Japan Body copy dealing with Japan Body copy dealing with Japan Body copy dealing with Japan Body co
|
| 30. |
|
| 31. |
|
| 32. |
|
| 33. |
|
| 34. |
|
| 35. |
This skill documents the **complete 6-file pattern** for building a Centralpoint ACTION EXT Module Designer: a data-centric grid with checkbox selection wired to a 3-step Wizard Action Form that performs bulk operations (Change Attributes, Move Modul
|
| 36. |
|
| 37. |
|
| 38. |
|
| 39. |
Guides creation of skill records inside the Centralpoint AI Prompt Manager console. Covers field structure, RTFEditor1 HTML template, trigger phrase standards, and post-save feed verification. Distinct from Claude .skill ZIP files — these are CP module re
|
| 40. |
This skill provides help documentation for Centralpoint security features.
|
| 41. |
Ensure every Excel spreadsheet generated for Centralpoint module import uses
|
| 42. |
Mail
|
| 43. |
HealthdayNews
|
| 44. |
VotingBallots
|
| 45. |
Coupons
|
| 46. |
Test
|
| 47. |
MemberProfiles
|
| 48. |
Ingestion Sources Click a source to start De-duplication Deduplicates via careful rules to store version history(ies) of older records under the latest. AI Enhancement Automates your indexed information to be AI summarized, or recommendations made to enhance. Data Governance Change record security or workflow status(es) based upon certain values found, including regex-supported mining. Automated Metadata Fully indexes each document or record, inc
|
| 49. |
Ingestion Sources Click a source to start De-duplication Deduplicates via careful rules to store version history(ies) of older records under the latest. AI Enhancement Automates your indexed information to be AI summarized, or recommendations made to enhance. Data Governance Change record security or workflow status(es) based upon certain values found, including regex-supported mining. Automated Metadata Fully indexes each document or record, inc
|
| 50. |
Forms are the primary interaction layer in Centralpoint applications. This skill covers creating forms, mapping data to modules, generating documents, and integrating with external systems.
|
| 51. |
Defines communication style for content directed at developers, solutions architects, data engineers, IT administrators, and other technical audiences. Precision, completeness, and actionability. Technical terminology expected and appropriate. Code sample
|
| 52. |
OTM
|
| 53. |
|